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 rtl-optimization/105661] Comparisons to atomic variables generates less efficient code
Date: Wed, 26 Oct 2022 23:34:08 +0000 [thread overview]
Message-ID: <bug-105661-4-kHeDXX51hx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105661-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105661
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |50677
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Severity|normal |enhancement
Component|target |rtl-optimization
Last reconfirmed| |2022-10-26
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The aarch64 issue is not really a big difference but it is the same issue
really.
Basically we don't optimize anything related to volatile memory even into the
address part. This is basically PR 50677 really.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50677
[Bug 50677] volatile forces load into register
next prev parent reply other threads:[~2022-10-26 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 12:59 [Bug target/105661] New: " redbeard0531 at gmail dot com
2022-10-26 23:34 ` pinskia at gcc dot gnu.org [this message]
2022-10-26 23:35 ` [Bug rtl-optimization/105661] " pinskia at gcc dot gnu.org
2023-02-09 18:11 ` 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-105661-4-kHeDXX51hx@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).