From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,e387f06de055df74
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.180.19.132 with SMTP id f4mr1035611wie.2.1359589039462;
        Wed, 30 Jan 2013 15:37:19 -0800 (PST)
MIME-Version: 1.0
X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 78.192.65.63
Path: 
 bp2ni7063wib.1!nntp.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!nntpfeed.proxad.net!news.muarf.org!news.ecp.fr!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Odd overflow exception being raised in one-line program
Date: Wed, 30 Jan 2013 17:37:16 -0600
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <kecare$uni$1@munin.nbi.dk>
References: <8259d65f-4b81-49d2-b1a0-613072c6b0fe@googlegroups.com>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1359589039 31474 69.95.181.76 (30 Jan 2013 23:37:19 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Wed, 30 Jan 2013 23:37:19 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Date: 2013-01-30T17:37:16-06:00
List-Id: <comp.lang.ada>

"Jerry" <lanceboyle@qwest.net> wrote in message 
news:8259d65f-4b81-49d2-b1a0-613072c6b0fe@googlegroups.com...
...
>This runs fine on my OS X 10.7.5 running GPL 2011 (20110419). The Ada
>binding in its present form has compiled on presumably numerous other 
>systems,
>including those of other developers, without this problem. The PLplot user 
>also
>reports several other overflow exceptions, all in a code base that has 
>never had
>such problems before.

I wonder if his hardware (you didn't say what processor/OS the person with 
the problem is running on) is either setting some bit incorrectly, or the 
bit is being interpreted wrong. I saw something like this when we 
implemented hardware conversions in Janus/Ada, as some weird bits were 
getting set that we misinterpreted as an error. It's possible to set up the 
Intel hardware to trap, and that could happen for underflow and other 
loss-of-precision cases, and such a trap would probably get reported as an 
overflow error.

It even possible that his OS has left some goofy setup in the floating point 
unit which causes bogus traps (bad device driver?). Did he try rebooting 
and/or running a "clean" system?

                                           Randy.