public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sje at cup dot hp.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/48823] gcc-4.6.0 floating-point optimization regression on ia64-Linux Date: Thu, 13 Oct 2011 17:58:00 -0000 [thread overview] Message-ID: <bug-48823-4-lmWsPkbUmW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48823-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48823 Steve Ellcey <sje at cup dot hp.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sje at cup dot hp.com Resolution| |INVALID --- Comment #3 from Steve Ellcey <sje at cup dot hp.com> 2011-10-13 17:57:50 UTC --- The difference in results is due to the use of the fma instructions (fused multiply add). If you don't want the fma instructions to be used you should use the -ffp-contract=on flag. Otherwise GCC will use them and accept the slightly different floating point results due to no rounding being done between the multiply and the add in the fma instruction. GCC will also do other optimizations that may change the results of inexact floating point instructions. I am resolving this as invalid since this change in the least significant bit of an inexact floating point value is reasonable without fp-contract being on.
next prev parent reply other threads:[~2011-10-13 17:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-29 14:14 [Bug rtl-optimization/48823] New: " mariah.lenox at gmail dot com 2011-05-02 9:21 ` [Bug rtl-optimization/48823] " jdemeyer at cage dot ugent.be 2011-05-02 9:32 ` jdemeyer at cage dot ugent.be 2011-10-13 17:58 ` sje at cup dot hp.com [this message] 2011-10-13 20:05 ` jdemeyer at cage dot ugent.be 2011-10-13 20:17 ` sje at cup dot hp.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=bug-48823-4-lmWsPkbUmW@http.gcc.gnu.org/bugzilla/ \ --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).