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/105458] [12/13 Regression] ICE in set_relation, at value-relation.cc:609
Date: Tue, 03 May 2022 06:52:59 +0000	[thread overview]
Message-ID: <bug-105458-4-T2xpffnYVC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105458-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-05-03
                 CC|                            |aldyh at gcc dot gnu.org,
                   |                            |amacleod at redhat dot com
     Ever confirmed|0                           |1
   Target Milestone|---                         |12.0
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |ice-checking

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  There is the unfolded t3_t > t3_6 which eventually makes us run
into
the assert.  We shouldn't assert that everything is correctly folded so we have
to be forgiving here (maybe just not registering anything here).  It might be
that when setting name1 == name2 that we'd run into compile-time issues.
Andrew should know how to avoid this ICE best.

<bb 3> [local count: 117688337]:
_7 = t3_6 > t3_6;
_8 = t3_6 == j4_5(D);
_9 = _8 | _7;
if (_9 != 0)
  goto <bb 4>; [7.19%]
else
  goto <bb 10>; [92.81%]

  reply	other threads:[~2022-05-03  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03  3:25 [Bug tree-optimization/105458] New: " asolokha at gmx dot com
2022-05-03  6:52 ` rguenth at gcc dot gnu.org [this message]
2022-05-03  8:44 ` [Bug tree-optimization/105458] [12/13 Regression] ICE in set_relation, at value-relation.cc:609 since r12-4790-g4b3a325f07acebf4 marxin at gcc dot gnu.org
2022-05-06  8:33 ` jakub at gcc dot gnu.org
2022-05-17 15:44 ` cvs-commit at gcc dot gnu.org
2022-05-18 14:13 ` cvs-commit at gcc dot gnu.org
2022-07-26 11:36 ` rguenth 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-105458-4-T2xpffnYVC@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).