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 ipa/99373] unused static function not being removed in some cases after optimization
Date: Thu, 04 Mar 2021 08:44:26 +0000 [thread overview]
Message-ID: <bug-99373-4-6wLcYPBj3Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99373-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99373
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-03-04
CC| |hubicka at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is only IPA reference promotes 'd' constant and thus only late
optimization elides the call to 'j'. That's too late to eliminate the
function.
Note we process 'j' first duing late opts (to make the late local IPA
pure-const
useful).
We'd need another IPA phase before RTL expansion to collect unreachable
functions again (IIRC the original parallel compilation GSoC project added
one).
I'm also quite sure we have a duplicate of this PR.
next prev parent reply other threads:[~2021-03-04 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 23:11 [Bug ipa/99373] New: [missed optimization] dead code not eliminated from short circuiting zhendong.su at inf dot ethz.ch
2021-03-04 0:06 ` [Bug ipa/99373] unused static function not being removed in some cases after optimization pinskia at gcc dot gnu.org
2021-03-04 8:44 ` rguenth at gcc dot gnu.org [this message]
2021-03-05 0:00 ` zhendong.su at inf dot ethz.ch
2023-01-10 18:25 ` 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-99373-4-6wLcYPBj3Y@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).