public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/111384] missed optimization: GCC adds extra any extend when storing subreg#0 multiple times
Date: Sat, 07 Oct 2023 20:54:03 +0000 [thread overview]
Message-ID: <bug-111384-4-DX4Eu0MKss@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111384-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111384
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-10-07
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #4 from Jeffrey A. Law <law at gcc dot gnu.org> ---
So this is something we've been pondering over in rv64 land. Joern has an
extension to DCE which tracks subobjects in an attempt to determine if bits set
by sign/zero extensions are never read. If they aren't read, then the
extension can be eliminated.
next prev parent reply other threads:[~2023-10-07 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 9:25 [Bug middle-end/111384] New: " lis8215 at gmail dot com
2023-09-12 12:38 ` [Bug rtl-optimization/111384] " rguenth at gcc dot gnu.org
2023-09-12 13:10 ` lis8215 at gmail dot com
2023-09-12 15:27 ` pinskia at gcc dot gnu.org
2023-09-12 15:35 ` pinskia at gcc dot gnu.org
2023-10-07 20:54 ` law at gcc dot gnu.org [this message]
2023-11-01 6:30 ` lis8215 at gmail 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-111384-4-DX4Eu0MKss@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).