From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 50466385840F; Tue, 3 May 2022 06:52:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 50466385840F From: "rguenth at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: ice-checking, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on cc everconfirmed target_milestone bug_status keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2022 06:52:59 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105458 Richard Biener 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 --- 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 =3D=3D name2 that we'd run into compile-time issues. Andrew should know how to avoid this ICE best. [local count: 117688337]: _7 =3D t3_6 > t3_6; _8 =3D t3_6 =3D=3D j4_5(D); _9 =3D _8 | _7; if (_9 !=3D 0) goto ; [7.19%] else goto ; [92.81%]=