------- Comment #6 from bugzilla at bennee dot com 2007-01-15 17:34 -------
(In reply to comment #5)
> and this is a bug why?
>
Well for starters why should the act of #include'ing stdlib.h cause any
instructions to be emitted if strtold isn't even invoked?
I don't understand exactly what the relationship between the -O options and
-mno-80387 is. I got lost in a maze of glibc headers trying to work out exactly
what getting instantiated. As far as I can tell it boils down to (gccs?)
internal implementation of strtold.
However if the -mno-80387 option is meant to disable x87 instructions then it
should be possible to build something without causing and x87 instructions to
be emitted shouldn't it?
The reason I want to disable the x87 is otherwise Signalling NaN's can get
silently supressed being passed through the x87 unit. I didn't want that and
wanted my SIGFPE's to be generated in some SSE code I had written.
Or does your question imply this is not gcc's problem but something in glibc?
--
bugzilla at bennee dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|target |c++
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30470
