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 tree-optimization/103359] [12 Regression] Dead Code Elimination Regression at -O3 (trunk vs 11.2.0)
Date: Tue, 23 Nov 2021 10:11:41 +0000	[thread overview]
Message-ID: <bug-103359-4-OycNnOG2m7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103359-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldyh at gcc dot gnu.org

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the important part is to eliminate the store to 'c' which GCC11 manages to
do
from EVRP while trunk fails at this task.  The IL into EVRP is absoultely
identical:

  <bb 2> :
  goto <bb 8>; [INV]

  <bb 8> :
  # h_10 = PHI <4(2), h_10(3), h_10(4), 1(7)>
  d.2_8 = d;
  if (d.2_8 != 0)
    goto <bb 3>; [INV]

  <bb 3> :
  if (h_10 != 0)
    goto <bb 4>; [INV]

  <bb 4> :
  e.0_1 = e;
  if (e.0_1 != 0)
    goto <bb 5>; [INV]

  <bb 5> :
  a.1_2 = a;
  _3 = (short int) a.1_2;
  _14 = a.1_2 & 1;
  _4 = (short int) _14;
  _5 = _4 | h_10;
  _6 = (int) _5;
  f.4_21 = (unsigned short) _5;
  _23 = f.4_21 * 3;
  _24 = (short int) _23;
  if (_5 == 0)
    goto <bb 6>; [INV]
  else
    goto <bb 7>; [INV]

  <bb 6> :
  c = 0;

  parent reply	other threads:[~2021-11-23 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 15:34 [Bug tree-optimization/103359] New: " theodort at inf dot ethz.ch
2021-11-22 22:04 ` [Bug tree-optimization/103359] " pinskia at gcc dot gnu.org
2021-11-22 22:23 ` pinskia at gcc dot gnu.org
2021-11-23  7:30 ` rguenth at gcc dot gnu.org
2021-11-23 10:11 ` rguenth at gcc dot gnu.org [this message]
2021-11-23 11:16 ` rguenth at gcc dot gnu.org
2021-11-23 11:36 ` rguenth at gcc dot gnu.org
2021-11-23 11:37 ` rguenth at gcc dot gnu.org
2021-11-23 13:09 ` aldyh at gcc dot gnu.org
2021-11-23 13:13 ` aldyh at gcc dot gnu.org
2021-11-23 16:03 ` amacleod at redhat dot com
2021-11-25 13:44 ` cvs-commit at gcc dot gnu.org
2021-11-25 13:45 ` amacleod at redhat dot com

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-103359-4-OycNnOG2m7@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).