public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "albin at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109344] New: feraiseexcept produces incorrect code when optimizations are enabled Date: Thu, 30 Mar 2023 07:49:01 +0000 [thread overview] Message-ID: <bug-109344-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109344 Bug ID: 109344 Summary: feraiseexcept produces incorrect code when optimizations are enabled Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: albin at yahoo dot com Target Milestone: --- At -O1, calls to feraiseexcept are inlined. But the inlined code produces incorrect results. See here, only the first function behaves as expected: https://godbolt.org/z/ncc3cjoKh The behavior persists across many versions. (A side note, I don't understand how the first function works, in order to produce a divbyzero exception it appears to divide 0 / 1, not 1 / 0, am I reading the assembly wrong?)
next reply other threads:[~2023-03-30 7:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-30 7:49 albin at yahoo dot com [this message] 2023-03-30 10:17 ` [Bug c++/109344] " xry111 at gcc dot gnu.org 2023-03-30 11:09 ` jakub at gcc dot gnu.org 2023-03-30 11:21 ` xry111 at gcc dot gnu.org 2023-03-30 12:18 ` albin at yahoo dot com 2023-03-30 12:23 ` xry111 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-109344-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).