[Bug c/60413] extra precision not properly removed on assignment of return value

2014-03-04 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60413 --- Comment #5 from Dominique d'Humieres --- I think this is another duplicate of pr323.

[Bug c/60413] extra precision not properly removed on assignment of return value

2014-03-04 Thread desrt at desrt dot ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60413 --- Comment #4 from Ryan Lortie --- It seems like a good solution to this problem might be to enable -mfpmath=sse by default on arches where SSE is known to be supported and -fexcess-precision=standard otherwise. If people want their binaries to

[Bug c/60413] extra precision not properly removed on assignment of return value

2014-03-04 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60413 --- Comment #3 from Jakub Jelinek --- (In reply to Ryan Lortie from comment #2) > Why is this violation of standards treated in a special way? Because it slows down things way too much. Much better is just to use -msse2 -mfpmath=sse if you reall

[Bug c/60413] extra precision not properly removed on assignment of return value

2014-03-04 Thread desrt at desrt dot ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60413 --- Comment #2 from Ryan Lortie --- Why is this violation of standards treated in a special way? Quoting from gcc's manpage: -ffast-math Sets -fno-math-errno, -funsafe-math-optimizations, -ffinite-math-only, -fno-rou

[Bug c/60413] extra precision not properly removed on assignment of return value

2014-03-04 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60413 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|