search for: signaling_nan

...ations must be rounded). - this can be represented with a 'exact_precision' bit 3) exceptions, you might need to have the right number of exceptions triggered in the right order so basically no optimizations are allowed. - this can be represented with a 'trapping_math' and/or 'signaling_NaN' bit, or maybe it can be encoded as 'no_reorder' 'no_duplicate' see: http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html (look for -ffloat-store) http://msdn.microsoft.com/en-us/library/e7s85ffb.aspx (Title: /fp (Specify Floating-Point Behavior)) - Morten

On Jan 14, 2010, at 2:01 AM, Duncan Sands wrote: > Hi Bill, > >> The current implementation of the "allow unsafe math" option is to >> specify it via the TargetOptions object. However, this prevents the >> target-independent optimizer from using it. Are there any opinions >> (ha!) on how this could be achieved in a nice clean manner which >>

...n via llvm-dev wrote: > > I am seeing failures in two tests after migrating to v5.0 final, these > are: > > std/language.support/support.limits/limits/numeric.limits.members/quiet_NaN.pass.cpp > > and: > > std/language.support/support.limits/limits/numeric.limits.members/signaling_NaN.pass.cpp > > However, these are new tests and it turns out that the underlying > problem is that the builtin ‘__builtin_nanl(“”)’ is returning the > value 0x0000000000000000.  I tested this builtin with our v4.0 > compiler and it has the same problem, so this is not a regression b...

I am seeing failures in two tests after migrating to v5.0 final, these are: std/language.support/support.limits/limits/numeric.limits.members/quiet_NaN. pass.cpp and: std/language.support/support.limits/limits/numeric.limits.members/signaling_ NaN.pass.cpp However, these are new tests and it turns out that the underlying problem is that the builtin '__builtin_nanl("")' is