public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla at bennee dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes
Date: Mon, 15 Jan 2007 17:34:00 -0000 [thread overview]
Message-ID: <20070115173420.7563.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30470-13920@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2007-01-15 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 9:09 [Bug c++/30470] New: " bugzilla at bennee dot com
2007-01-15 9:14 ` [Bug c++/30470] " bugzilla at bennee dot com
2007-01-15 9:16 ` bugzilla at bennee dot com
2007-01-15 9:18 ` bugzilla at bennee dot com
2007-01-15 15:25 ` ubizjak at gmail dot com
2007-01-15 17:04 ` [Bug target/30470] " pinskia at gcc dot gnu dot org
2007-01-15 17:34 ` bugzilla at bennee dot com [this message]
2007-01-15 17:45 ` [Bug c++/30470] " pinskia at gcc dot gnu dot org
2007-01-16 11:28 ` bugzilla at bennee dot com
2007-01-17 6:59 ` ubizjak at gmail dot com
2007-01-17 10:35 ` bugzilla at bennee dot com
2007-01-17 12:40 ` ubizjak at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070115173420.7563.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).