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/94818] GCC emits dead bodies of functions whose all calls have been eliminated by optimisations
Date: Tue, 28 Apr 2020 13:36:15 +0000 [thread overview]
Message-ID: <bug-94818-4-2MLKBBn4s5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94818-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94818
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2020-04-28
CC| |marxin at gcc dot gnu.org
Component|tree-optimization |ipa
Status|UNCONFIRMED |NEW
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. ___builtin_constant_p is only resolved after IPA optimization and
at that point unreachable functions can no longer be removed reliably
(foo is output before bar0 __builtin_constant_p is resolved).
We could add another "IPA" sync point before RTL expansion but not sure if
we really want to.
We could also see there's no callers to bar0 and bar1 and resolve
__builtin_constant_p earlier during IPA.
next prev parent reply other threads:[~2020-04-28 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 12:43 [Bug tree-optimization/94818] New: " felix.von.s at posteo dot de
2020-04-28 13:36 ` rguenth at gcc dot gnu.org [this message]
2020-04-29 6:27 ` [Bug ipa/94818] " pinskia at gcc dot gnu.org
2021-07-20 22:23 ` 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-94818-4-2MLKBBn4s5@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).