public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pdimov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110477] New: -fexcess-precision=standard not applied consistently Date: Thu, 29 Jun 2023 07:28:39 +0000 [thread overview] Message-ID: <bug-110477-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 Bug ID: 110477 Summary: -fexcess-precision=standard not applied consistently Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pdimov at gmail dot com Target Milestone: --- The following program float f( float x, int y ) { return x + y; } int main() { return f( 3.14f, 1 ) == 3.14f + 1; } returns different values with -std=c++XX (https://godbolt.org/z/8dK98ondM) and -std=gnu++XX (https://godbolt.org/z/4Y4qfsKzM) under GCC 13/14 -m32, because -fexcess-precision=standard is not consistently applied to both sides of the comparison. Under -fexcess-precision=fast (and hence under previous GCC versions), the comparison always succeeds because both sides use excess precision (https://godbolt.org/z/dzdoxdnM9). This is the runtime equivalent of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110476.
next reply other threads:[~2023-06-29 7:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-29 7:28 pdimov at gmail dot com [this message] 2023-06-29 8:00 ` [Bug c++/110477] " pdimov at gmail dot com 2023-06-29 8:04 ` pinskia at gcc dot gnu.org 2023-06-29 8:10 ` pdimov at gmail dot com 2023-06-29 8:31 ` redi at gcc dot gnu.org 2023-06-29 8:32 ` redi at gcc dot gnu.org 2023-06-29 8:44 ` pdimov at gmail dot com 2023-06-29 9:07 ` mkretz at gcc dot gnu.org 2023-06-29 11:00 ` pdimov 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=bug-110477-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).