From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 20AD7385841A; Fri, 16 Feb 2024 08:29:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 20AD7385841A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1708072183; bh=UCKT0kO7UVmxKotV247duKStKPWk98nW0ueSU8ecfUQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bR3hExMDU/vz7jukRpZIM+pnQpQGOt8d3mG7K+Niy1x8HaFOJgRaU7N+g+RUe4XrX QsuJtT8lY6AvE83FMqxtqoGivaett+s7U79gjwnOK4JyL25YNU+RK9SqHsEVUnWZ0E 3r/tguNwYO1h84ozYsxNuPBnyQ1Q08o29kYvViG4= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113898] [14 regression] ICE in copy_reference_ops_from_ref, at tree-ssa-sccvn.cc:1156 since r14-8929-g938a419182f Date: Fri, 16 Feb 2024 08:29:42 +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: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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=3D113898 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Richard Biener --- Yes, that case is tracked in PR113895 - we value number e[h_7(D)][1] =3D 4; and out-of-bound array indices behave differently, choking the verifier cod= e. And I don't see an easy way to fix that so the plan is to remove the verifi= er code (not sure if it's worth detecting those cases and selectively disabling it). Let's track this in the other bug.=