From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 27F4B3858C74; Thu, 2 Feb 2023 15:11:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 27F4B3858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675350665; bh=4VyC4PlV1S3fWxdMvQ+ZeCXjcyxvhViopHx/xftC60g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=a0hpaBH4BO0SDe2+NMDSDxgPNEU2Ync6CNS/qvo/Ty0tNrIXv5XtMtGf86TOTGdVy nmYTJj5fUUBP4rv37Lc570w7l+FhUpgcKaQDiyn0CwHXL8tWllV17mnyKQHvllmBXe Bh4G/2VRxtq/PMgPZaPGw7b3t1IFadBYG/WadQ8A= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108639] ]13 Regression] ICE on valid code at -O1 and above: in decompose, at wide-int.h:984 since r13-5578 Date: Thu, 02 Feb 2023 15:11:04 +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: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108639 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amacleod at redhat dot com --- Comment #2 from Jakub Jelinek --- The problem is in 271 if (relation_equiv_p (rel) && lh =3D=3D rh) We see # RANGE [irange] int [0, 1] NONZERO 0x1 # iftmp.0_6 =3D PHI <_10(3), 0(2)> # RANGE [irange] long int [0, 1] NONZERO 0x1 _3 =3D (long int) iftmp.0_6; # RANGE [irange] unsigned int [0, 1] NONZERO 0x1 _4 =3D (unsigned int) iftmp.0_6; # RANGE [irange] long int [-INF, +INF] NONZERO 0x3 _5 =3D _3 << _4; so lhs and rhs indeed have the same range, but unlike most binary operation= s, shifts/rotates have the same type between lhs and rhs1, but rhs2 can have different type. So, the lh =3D=3D rh comparison ICEs because the wide_ints have different p= recision (but same values).=