public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nok.raven at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100858] Simple common code hoisting is not performed
Date: Wed, 02 Jun 2021 23:18:12 +0000	[thread overview]
Message-ID: <bug-100858-4-YXBDwLor3i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100858-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Nikita Kniazev <nok.raven at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> That's really a duplicate of 100858 - this case can be handled by sinking as
> well
> since we "sink" the return.  Make it
> 
> void bar();
> 
> int foo(bool f)
> {
>     if (f) {
>         bar();
>         __builtin_abort ();
>     }
>     else {
>         bar();
>         return 2;
>     }
> }
> to force hoisting.

I have a hard time in finding this as equivalent to the original code.

> Hoisting is done by PRE but that requires a LHS and doesn't handle calls with side-effects.

That seems like an artificial limitation. Why we cannot hoist the bar call?

  parent reply	other threads:[~2021-06-02 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 15:16 [Bug tree-optimization/100858] New: " nok.raven at gmail dot com
2021-06-02  8:01 ` [Bug tree-optimization/100858] " rguenth at gcc dot gnu.org
2021-06-02 23:18 ` nok.raven at gmail dot com [this message]
2021-07-28 20:17 ` 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-100858-4-YXBDwLor3i@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).