public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/52907] New: Underflowing floating point expressions wrongly folded to zero Date: Sun, 08 Apr 2012 21:45:00 -0000 [thread overview] Message-ID: <bug-52907-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52907 Bug #: 52907 Summary: Underflowing floating point expressions wrongly folded to zero Classification: Unclassified Product: gcc Version: 4.6.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: jsm28@gcc.gnu.org fold-const.c:const_binop avoids folding overflowing floating-point operations on constant operands to constants if flag_trapping_math: /* Don't constant fold this floating point operation if the result has overflowed and flag_trapping_math. */ if (flag_trapping_math && MODE_HAS_INFINITIES (mode) && REAL_VALUE_ISINF (result) && !REAL_VALUE_ISINF (d1) && !REAL_VALUE_ISINF (d2)) return NULL_TREE; However, there is no such check for underflow. This has the effect of miscompiling various code in glibc's libm that expects operations on constant values to be usable to produce an overflow or underflow exception when required. In particular, this appears to cause <http://sourceware.org/bugzilla/show_bug.cgi?id=10846>. Testcase, tested x86 and x86_64 (-O2 -ftrapping-math, wrongly compiled to return 0 rather than doing the given computation): static const double a = 1e-300; double f (void) { return a * a; }
next reply other threads:[~2012-04-08 21:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-08 21:45 jsm28 at gcc dot gnu.org [this message] 2012-04-10 12:20 ` [Bug tree-optimization/52907] " rguenth at gcc dot gnu.org 2012-04-23 20:03 ` joseph at codesourcery dot com 2024-03-11 0:09 ` [Bug middle-end/52907] " pinskia at gcc dot gnu.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=bug-52907-4@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).