Done. I went the ubuntu route just in case it is an ubuntu peculiarity.
https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/899596
Ed
On Fri, 2 Dec 2011, Tim Jenness wrote:
> I reproduced this on an ubuntu system. My quick fix suggestion is to
> use clang which does not have the bug (it's a standard package in
> ubuntu now). It seems to be a gcc 4.6.1 bug in 32-bit mode only (works
> fine with -m64). I imagine if you were motivated you should file a
> ubuntu fault since you already have the test script (they will pass it
> upstream after they have verified it if you aren't brave enough to
> talk to the gcc guys directly).
>
> Tim
>
> On Fri, Dec 2, 2011 at 3:24 PM, Edward L. Chapin <[log in to unmask]> wrote:
>>
>> Despite finally getting starlink to build on my 32bit Ubuntu 11.10 machine,
>> I started running into some odd run-time problems.
>>
>> I narrowed it down to some sort of problem comparing double-precision
>> variables with constants when I use the -std=c99 compiler flag.
>>
>> I've attached a minimal test program to this mail to demonstrate the problem
>> -- see the comments at the top for examples of the gcc calls that I do and
>> the output.
>>
>> I guess the solution is to drop the -std=c99, although it would be
>> interesting to know why this happens.
>>
>> Ed
>
|