[Bug target/53134] Request for option to disable excess precision on i387

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53134 --- Comment #8 from Rich Felker 2012-04-28 23:14:57 UTC --- I agree, sadly, that WONTFIX is probably the most appropriate action. At least, like Andrew said, we're getting to the point where assuming it's okay to build with -msse2 and -mfpmath=ss

[Bug target/53134] Request for option to disable excess precision on i387

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53134 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug target/53134] Request for option to disable excess precision on i387

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53134 --- Comment #6 from Rich Felker 2012-04-27 11:51:05 UTC --- Joseph, you're right, and I don't see any way to handle the denormal issue without really ugly and much slower wrapper code around each op...

[Bug target/53134] Request for option to disable excess precision on i387

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53134 --- Comment #5 from joseph at codesourcery dot com 2012-04-27 10:26:22 UTC --- See also what I said in : The option naming leaves open the possibility of other options such as "non

[Bug target/53134] Request for option to disable excess precision on i387

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53134 --- Comment #4 from joseph at codesourcery dot com 2012-04-27 10:23:42 UTC --- On Fri, 27 Apr 2012, bugdal at aerifal dot cx wrote: > Since even with the precision mode set correctly the exponent range of 387 fpu > registers still matches that of

[Bug target/53134] Request for option to disable excess precision on i387

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53134 Andrew Pinski changed: What|Removed |Added Component|c |target --- Comment #3 from Andrew Pinski