Re: bug report: not-a-number not recognized when compiling for x86_64

2013-01-15 Thread Mischa Baars
On 01/14/2013 03:50 PM, Marc Glisse wrote: On Mon, 14 Jan 2013, Mischa Baars wrote: When running the example attached, you can see the compiler fails to recognize not-a-number's properly. Bug reports go to bugzilla. NaN doesn't compare equal to anything. x==x is actually the usual way to te

Re: bug report: not-a-number not recognized when compiling for x86_64

2013-01-14 Thread Marc Glisse
On Mon, 14 Jan 2013, Mischa Baars wrote: When running the example attached, you can see the compiler fails to recognize not-a-number's properly. Bug reports go to bugzilla. NaN doesn't compare equal to anything. x==x is actually the usual way to test if x is NaN. -- Marc Glisse

Re: bug report: not-a-number not recognized when compiling for x86_64

2013-01-14 Thread Andrew Haley
On 01/14/2013 08:34 AM, Mischa Baars wrote: > When running the example attached, you can see the compiler fails to > recognize not-a-number's properly. > > Anyone who would like to have a look? Comparing NaN with anything always returns false. Even when comparing with NaN. You want: i

Re: bug report: not-a-number not recognized when compiling for x86_64

2013-01-14 Thread Richard Biener
On Mon, Jan 14, 2013 at 9:34 AM, Mischa Baars wrote: > Hi, > > When running the example attached, you can see the compiler fails to > recognize not-a-number's properly. > > Anyone who would like to have a look? THat's how FP works. Use isnan(). Richard. > Regards, > Mischa.