public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/112525] fail to eliminate unused store
Date: Tue, 14 Nov 2023 07:44:10 +0000	[thread overview]
Message-ID: <bug-112525-4-Wg5mvbPHb4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112525-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112525

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-11-14

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I wonder if optimizing for "unused" parameters is worth it (usually IPA SRA
will elide them).  "unused" could be computed by cfgexpand walking the body,
but
we do expect to be able to inspect those parameters with -g, so care has to
be taken that this works at all optimization levels.

  parent reply	other threads:[~2023-11-14  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  6:40 [Bug rtl-optimization/112525] New: " guojiufu at gcc dot gnu.org
2023-11-14  6:48 ` [Bug rtl-optimization/112525] " guojiufu at gcc dot gnu.org
2023-11-14  6:49 ` pinskia at gcc dot gnu.org
2023-11-14  7:01 ` guojiufu at gcc dot gnu.org
2023-11-14  7:44 ` rguenth at gcc dot gnu.org [this message]
2023-11-14  7:45 ` rguenth at gcc dot gnu.org
2023-11-15  1:49 ` guojiufu at gcc dot gnu.org
2023-12-19  5:18 ` cvs-commit at gcc dot gnu.org
2024-01-04  0:47 ` guojiufu 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-112525-4-Wg5mvbPHb4@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).