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 middle-end/116383] Value from __atomic_store not forwarded to non-atomic load at same address
Date: Thu, 15 Aug 2024 16:21:34 +0000 [thread overview]
Message-ID: <bug-116383-4-0CsikbIMC6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-116383-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116383
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Severity|normal |enhancement
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I am not sure this is a wanted optimization.
Note I also think the original code is questionable and maybe even has a race
condition in it.
>but on-thread reads should be safe using ordinary loads,
I don't think that is valid thing to do.
next prev parent reply other threads:[~2024-08-15 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 13:22 [Bug middle-end/116383] New: " redbeard0531 at gmail dot com
2024-08-15 16:21 ` pinskia at gcc dot gnu.org [this message]
2024-08-19 10:30 ` [Bug middle-end/116383] " redi at gcc dot gnu.org
2024-08-19 10:30 ` redi 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-116383-4-0CsikbIMC6@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).