public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108329] IEEE_SET_ROUNDING_MODE ineffective with common subexpression elimination Date: Sat, 07 Jan 2023 12:33:59 +0000 [thread overview] Message-ID: <bug-108329-4-yBNRWeuXUC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108329-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108329 Thomas Koenig <tkoenig at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unknown |13.0 Depends on| |34678 Keywords| |wrong-code Blocks| |105105 --- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- As long as PR 36678 is not fixed, I see one possible solution in putting a memory barrier after ieee_set_rounding_mode. This is a rather big hammer, but as long as the middle-end issue is not fixed, I do not see an alternative. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34678 [Bug 34678] Optimization generates incorrect code with -frounding-math option (#pragma STDC FENV_ACCESS not implemented) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105105 [Bug 105105] [Meta] Fortran IEEE support
next prev parent reply other threads:[~2023-01-07 12:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-07 12:24 [Bug fortran/108329] New: " tkoenig at gcc dot gnu.org 2023-01-07 12:33 ` tkoenig at gcc dot gnu.org [this message] 2023-01-07 12:47 ` [Bug fortran/108329] " tkoenig at gcc dot gnu.org 2023-01-07 15:50 ` tkoenig at gcc dot gnu.org 2023-01-09 15:27 ` tkoenig 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-108329-4-yBNRWeuXUC@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).