public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113282] RISC-V non-atomic union store/load reordering
Date: Mon, 08 Jan 2024 22:15:41 +0000	[thread overview]
Message-ID: <bug-113282-4-g0gNfEN4jo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113282-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113282

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> On x86 this problem

Yes x86 does not enable the scheduler before ra and has less registers so the
scheduler is not as aggressive as on the other targets.

Note this is standard strict aliasing issue even. Which is definitely mentioned
as a non issue even.

  parent reply	other threads:[~2024-01-08 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 21:25 [Bug target/113282] New: " patrick at rivosinc dot com
2024-01-08 22:13 ` [Bug target/113282] " pinskia at gcc dot gnu.org
2024-01-08 22:15 ` pinskia at gcc dot gnu.org [this message]
2024-01-08 22:16 ` pinskia at gcc dot gnu.org
2024-01-08 22:40 ` patrick at rivosinc dot com
2024-01-08 22:44 ` pinskia 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-113282-4-g0gNfEN4jo@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: link
Be 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).