public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91674] [ARM/thumb] redundant memcpy does not get optimized away on thumb
Date: Wed, 03 Aug 2022 17:25:07 +0000 [thread overview]
Message-ID: <bug-91674-4-YPG295CeGl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91674-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91674
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
This is essentially a dup of PR105090, which is now fixed on master. The code
generation in both Arm and Thumb2 state is essentially the same early on, but
in Thumb we were unable to optimize away all the byte manipulations.
The unused stack slot was needed at the time of early expansion to RTL and once
created there's no mechanism for getting rid of it if it is no-longer needed.
*** This bug has been marked as a duplicate of bug 105090 ***
parent reply other threads:[~2022-08-03 17:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-91674-4@http.gcc.gnu.org/bugzilla/>]
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-91674-4-YPG295CeGl@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).