[Bug target/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 --- Comment #19 from Charles L. Wilcox --- (In reply to Uroš Bizjak from comment #11) > On an x86 target using the legacy x87 instructions and the 80-bit registers, > a load of a 64-bit or 32-bit value in memory into the 80-bit registers > counts

[Bug target/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 --- Comment #17 from Charles L. Wilcox --- Okay... so why not avoid the x87 restriction and use aliasing to load the correct value? I've updated my example to show how I was doing exactly this for some unit-test code I created.

[Bug target/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 Charles L. Wilcox changed: What|Removed |Added Attachment #30239|0 |1 is obsolete|

[Bug middle-end/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 --- Comment #9 from Charles L. Wilcox --- So, given a month has gone by, should I expect any response or action on this bug-report?

[Bug middle-end/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 --- Comment #8 from Charles L. Wilcox --- FWIW, I tried this with g++ 4.8 on a 32-bit only system I have; it still produces erroneous sNaN values there: $ g++-4.8 -v Using built-in specs. COLLECT_GCC=g++-4.8 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-

[Bug c++/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 --- Comment #6 from Charles L. Wilcox --- (In reply to Paolo Carlini from comment #5) > Just to clarify that this is neither a library neither a C++ front-end > issue: just uses the various __builtin_nans* Paolo, I guessed this was the case fro

[Bug c++/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 --- Comment #3 from Charles L. Wilcox --- Daniel, Unfortunately, my initial machine, a laptop, decided to commit seppuku yesterday. Fortunately, the disk survived, I ported the code to another machine I have, and am still seeing similar results

[Bug c++/57484] 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484 Charles L. Wilcox changed: What|Removed |Added Attachment #30234|0 |1 is obsolete|

[Bug c++/57484] New: 'std::numeric_limits< T >::signaling_NaN()' signaling-bit is incorrect for x86 32-bit.

tus: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zxClhzAApX1EdJwQANqrjLERmFeURQVy at cynd dot net Created attachment 30234 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30234&action=e