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/111465] [14 regression] stage 3 ICE kills bootstrap from r14-4089-gd45ddc2c04e471d0dcee01
Date: Tue, 19 Sep 2023 10:19:18 +0000	[thread overview]
Message-ID: <bug-111465-4-cioFCg0fvf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111465-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=102844
                 CC|                            |law at gcc dot gnu.org

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
So we simplify


 if (iftmp.2_137 <= location_138)
   ..
 else
   {
     _16 = (signed) prephitmp_15;
     if (_16 < 0)
...

to

 _192 = (signed) location_138;
 if (0)
   ..
 else
  {
     _16 = (signed) prephitmp_15;
     if (_16 < 0)
...

and then thread - actually we have registered the forward thread already
and registered the block with the def of _192 as EDGE_NO_COPY_SRC_BLOCK
(because it was empty before).  This is essentially a duplicate of PR102844
which has gone latent.

  parent reply	other threads:[~2023-09-19 10:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 20:26 [Bug bootstrap/111465] New: [14 regression] stage 3 ICE kills bootstrap seurer at gcc dot gnu.org
2023-09-18 20:48 ` [Bug tree-optimization/111465] " pinskia at gcc dot gnu.org
2023-09-18 21:41 ` seurer at gcc dot gnu.org
2023-09-18 21:54 ` pinskia at gcc dot gnu.org
2023-09-18 22:32 ` [Bug tree-optimization/111465] [14 regression] stage 3 ICE kills bootstrap from r14-4089-gd45ddc2c04e471d0dcee01 pinskia at gcc dot gnu.org
2023-09-18 22:40 ` pinskia at gcc dot gnu.org
2023-09-18 23:23 ` pinskia at gcc dot gnu.org
2023-09-18 23:30 ` pinskia at gcc dot gnu.org
2023-09-19  9:16 ` rguenth at gcc dot gnu.org
2023-09-19 10:19 ` rguenth at gcc dot gnu.org [this message]
2023-09-19 10:39 ` rguenth at gcc dot gnu.org
2023-09-19 11:24 ` cvs-commit at gcc dot gnu.org
2023-09-19 11:24 ` rguenth at gcc dot gnu.org
2023-11-24 15:13 ` cvs-commit 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-111465-4-cioFCg0fvf@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).