public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lis8215 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/60749] combine is overly cautious when operating on volatile memory references
Date: Fri, 26 May 2023 13:56:35 +0000 [thread overview]
Message-ID: <bug-60749-4-GTmBxm8NU9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60749-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60749
Siarhei Volkau <lis8215 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lis8215 at gmail dot com
--- Comment #2 from Siarhei Volkau <lis8215 at gmail dot com> ---
Created attachment 55167
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55167&action=edit
allow combine ld/st of volatile mem with any_extend op
Is anyone bothering on that? I'm, as embedded engineer, sadly looking on that
long standing issue.
I can propose a quick patch which enables combining volatile mem ld/st with
any_extend for most cases. And it seems, like platform specific test results
remain the same with it (arm/aarch64/mips were tested).
Post it in hope it can help for anyone who needs it.
next prev parent reply other threads:[~2023-05-26 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 15:41 [Bug rtl-optimization/60749] New: " amylaar at gcc dot gnu.org
2022-02-04 20:55 ` [Bug rtl-optimization/60749] " pinskia at gcc dot gnu.org
2023-05-26 13:56 ` lis8215 at gmail dot com [this message]
2023-09-25 7:09 ` cptarse-luke at yahoo dot com
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-60749-4-GTmBxm8NU9@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).