public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/35202] [4.1/4.2/4.3 Regression] exp->expf transformation incorrect with -fmath-errno Date: Thu, 14 Feb 2008 23:02:00 -0000 [thread overview] Message-ID: <20080214230136.20536.qmail@sourceware.org> (raw) In-Reply-To: <bug-35202-230@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2008-02-14 23:01 ------- There are more problems with -ferrno-math, see also PR29887. It is btw unclear to me whether -ferrno-math is supposed to preserve errno handling of whatever the underlying libm provides or if it should actively do errno handling for errors required by the standard or also for those that are optional by the standard. That is specifically how this option relates to 7.12.1, especially if -ferrno-math effectively constrains the value of math_errhandling or makes GCC assume a certain value of it. Also what the effects of -ferrno-math are on the subtle difference of "a ... error occurs" and "a ... error may occur". Clarification would be much appreciated here, and I would like to effectively make our default (-ferrno-math -ftrapping-math) be changed to -fno-errno-math -ftrapping-math and providing math_errhandling == MATH_ERREXCEPT by GCC, overriding the library. Actually 7.12.1 does not say that errno is untouched if math_errhandling == MATH_ERREXCEPT, or does it do so implicitly? Yet another reason why separating the math runtime from GCC is bad :( -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu dot | |org Keywords| |wrong-code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35202
next prev parent reply other threads:[~2008-02-14 23:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-14 22:03 [Bug tree-optimization/35202] New: " jsm28 at gcc dot gnu dot org 2008-02-14 22:10 ` [Bug tree-optimization/35202] " pinskia at gcc dot gnu dot org 2008-02-14 23:02 ` rguenth at gcc dot gnu dot org [this message] 2008-02-14 23:10 ` joseph at codesourcery dot com 2008-02-15 15:51 ` rguenth at gcc dot gnu dot org 2008-02-15 15:54 ` rguenth at gcc dot gnu dot org 2008-02-15 21:51 ` joseph at codesourcery dot com 2008-07-04 22:34 ` [Bug tree-optimization/35202] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2009-01-25 18:29 ` rguenth at gcc dot gnu dot org 2009-02-09 9:35 ` rguenth at gcc dot gnu dot org 2009-02-09 9:36 ` rguenth at gcc dot gnu dot org
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=20080214230136.20536.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: linkBe 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).