public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luke.geeson at cs dot ucl.ac.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111246] PPC64 Sequentially Consistent Load allows Reordering of Stores Date: Wed, 30 Aug 2023 20:35:53 +0000 [thread overview] Message-ID: <bug-111246-4-pdRYRHWGFr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111246-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111246 --- Comment #1 from Luke Geeson <luke.geeson at cs dot ucl.ac.uk> --- Edit: The godbolt link points to the same bug in LLVM I am reporting, here is the GCC godbolt link https://godbolt.org/z/Tan5jrvKa
next prev parent reply other threads:[~2023-08-30 20:35 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-30 20:23 [Bug target/111246] New: " luke.geeson at cs dot ucl.ac.uk 2023-08-30 20:35 ` luke.geeson at cs dot ucl.ac.uk [this message] 2023-08-30 20:38 ` [Bug target/111246] " pinskia at gcc dot gnu.org 2023-08-30 20:47 ` luke.geeson at cs dot ucl.ac.uk 2023-08-30 20:49 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 13:41 ` dje at gcc dot gnu.org 2023-08-31 13:49 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 16:23 ` dje at gcc dot gnu.org 2023-08-31 18:04 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 18:06 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 18:25 ` dje at gcc dot gnu.org 2023-08-31 18:54 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 18:58 ` pinskia at gcc dot gnu.org 2023-08-31 19:12 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 20:00 ` dje at gcc dot gnu.org 2023-08-31 20:49 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 20:50 ` luke.geeson at cs dot ucl.ac.uk 2023-08-31 20:52 ` dje at gcc dot gnu.org 2023-08-31 20:55 ` luke.geeson at cs dot ucl.ac.uk
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-111246-4-pdRYRHWGFr@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).