[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2019-12-09 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #13 from joseph at codesourcery dot com --- On Fri, 6 Dec 2019, vgupta at synopsys dot com wrote: > However I'm curious that the test uses qNaN. What is the expected behavior for > sNaN. If you tweak the testcase slightly as

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2019-12-06 Thread vgupta at synopsys dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #12 from Vineet Gupta --- oops the ARC bug is (PR 92846) not (PR 92845)

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2019-12-06 Thread vgupta at synopsys dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 Vineet Gupta changed: What|Removed |Added CC||vgupta at synopsys dot com --- Comment

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2017-12-18 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #10 from joseph at codesourcery dot com --- Please file a separate bug for hppa, just as we have separate bugs for the powerpc and s390 back end issues. Assuming hppa-hpux has working fenv.h, failure on hppa is probably a back-end

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2017-12-17 Thread danglin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 John David Anglin changed: What|Removed |Added CC||danglin at gcc dot gnu.org ---

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2017-10-23 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #8 from Uroš Bizjak --- (In reply to seurer from comment #7) > Shouldn't the new test case have been marked XFAIL for powerpc64 and s390? > It fails on powerpc64 for sure. This is up to target maintainer. XFAIL will get the problem

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2017-10-23 Thread seurer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 seurer at gcc dot gnu.org changed: What|Removed |Added CC||seurer at gcc dot gnu.org

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2017-10-22 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 Uroš Bizjak changed: What|Removed |Added Target||x86 Status|WAITING

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2017-10-22 Thread uros at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #5 from uros at gcc dot gnu.org --- Author: uros Date: Sun Oct 22 19:04:36 2017 New Revision: 253986 URL: https://gcc.gnu.org/viewcvs?rev=253986=gcc=rev Log: PR target/52451 * config/i386/i386.c

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2014-09-11 Thread nszabolcs at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 Szabolcs Nagy nszabolcs at gmail dot com changed: What|Removed |Added CC||nszabolcs at

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2012-04-23 Thread bugdal at aerifal dot cx
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #3 from Rich Felker bugdal at aerifal dot cx 2012-04-23 09:37:45 UTC --- Compiling with the -mno-ieee-fp option fixes this bug. It seems like the behavior of this option is reversed from the documentation; -mno-ieee-fp gives IEEE

[Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons

2012-03-15 Thread bugdal at aerifal dot cx
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451 --- Comment #2 from Rich Felker bugdal at aerifal dot cx 2012-03-15 16:23:11 UTC --- Try foo(NAN,NAN) and then check for the INVALID exception. It's not set.