public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108298] Wrong optimization of volatile access from gcc 11 and beyond Date: Thu, 05 Jan 2023 11:25:29 +0000 [thread overview] Message-ID: <bug-108298-4-F2X8eO9T5c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108298-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |--- Last reconfirmed| |2023-01-05 Status|RESOLVED |NEW Ever confirmed|0 |1 CC| |segher at gcc dot gnu.org --- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> --- This is not a dup of 33053 (see PR33053#c5 and PR33053#c6). Reopening, and confirmed. There should be a read from memory: that is a side effect, it has to be executed in the real machine as in the abstract machine.
next prev parent reply other threads:[~2023-01-05 11:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-05 9:09 [Bug c/108298] New: " daniel.lundin.mail at gmail dot com 2023-01-05 9:18 ` [Bug c/108298] " pinskia at gcc dot gnu.org 2023-01-05 11:25 ` segher at gcc dot gnu.org [this message] 2023-01-05 11:29 ` daniel.lundin.mail at gmail dot com 2023-01-05 14:55 ` segher at gcc dot gnu.org 2023-01-05 17:10 ` segher at gcc dot gnu.org 2023-01-06 11:21 ` [Bug middle-end/108298] " marxin at gcc dot gnu.org 2023-01-06 16:52 ` pinskia at gcc dot gnu.org 2023-01-09 11:50 ` rguenth at gcc dot gnu.org 2023-01-09 13:53 ` segher at gcc dot gnu.org 2023-01-09 13:55 ` rguenther at suse dot de
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-108298-4-F2X8eO9T5c@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).