public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/99835] missed optimization for dead code elimination at -O3 (vs. -O1)
Date: Wed, 31 Mar 2021 09:10:59 +0000	[thread overview]
Message-ID: <bug-99835-4-ED2Mkt1BgY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99835-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jan Hubicka <hubicka at ucw dot cz> ---
> But inside a SCC the order is arbitrary anyway.  Note I'd only re-order SCCs
> and keep the postordering the same otherwise.

We compile leaf functions first to be able to propagated to their
callers.  In order to be able to optimize out functions in case call was
optimized out, we would need to compile in reverse order than we do
now...

Honza

  parent reply	other threads:[~2021-03-31  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 17:27 [Bug tree-optimization/99835] New: " zhendong.su at inf dot ethz.ch
2021-03-31  8:08 ` [Bug ipa/99835] " rguenth at gcc dot gnu.org
2021-03-31  8:14   ` Jan Hubicka
2021-03-31  8:14 ` hubicka at ucw dot cz
2021-03-31  8:17 ` rguenth at gcc dot gnu.org
2021-03-31  9:10 ` hubicka at ucw dot cz [this message]
2021-09-25  7:20 ` 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-99835-4-ED2Mkt1BgY@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).