public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114489] introduced redundant load facing different branches
Date: Tue, 26 Mar 2024 20:19:31 +0000	[thread overview]
Message-ID: <bug-114489-4-CbdygcKOzF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114489-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
>   <bb 3> [local count: 375809640]:
>   _3 = g1;
>   goto <bb 5>; [100.00%]
> 
>   <bb 4> [local count: 697932184]:
>   g2.1_2 = g2;
>   arr[0] = g2.1_2;
>   _8 = g1;
> 
>   <bb 5> [local count: 1073741824]:
>   # _6 = PHI <_8(4), _3(3)>
> 
> Which does not optimize unless using -O2.
> 
> This is on purpose.

In that PRE is not enabled at -O1 but it is at -O2.

      parent reply	other threads:[~2024-03-26 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 20:09 [Bug tree-optimization/114489] New: " absoler at smail dot nju.edu.cn
2024-03-26 20:18 ` [Bug tree-optimization/114489] " pinskia at gcc dot gnu.org
2024-03-26 20:19 ` pinskia at gcc dot gnu.org [this message]

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-114489-4-CbdygcKOzF@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).