From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8484A3860745; Tue, 7 Nov 2023 16:11:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8484A3860745 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1699373495; bh=H6IjCKcWRsP3O01NucZN5xmQGdN53mbgOpQYEquE5Ss=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JhJvGTGBS7imp4JHvz/S7uKae0BpRGnwiZiC1vp9porxGkTOm/GO1plgj8uB+k7+u oDpOslWDDavZ4dQzm9roYxwEwfZOhv6M8ktOKn4cQ8kYR3Pc/PJBmfnri+8DNu4Npi iNxql5kIrzXMActVq/718ZT/uxaoaZxDDYZCFvy4= From: "saurabh.jha at arm dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112337] arm: ICE in arm_effective_regno when compiling for MVE Date: Tue, 07 Nov 2023 16:11:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: saurabh.jha at arm dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D112337 --- Comment #5 from Saurabh Jha --- Hey, I did some digging into it. The ICE is happening on this assert: gcc_assert (REG_P (op)) Here the op->code is MEM while it was expecting a REG. For the test program above, the function arm_effective_regno is called some number of times and = that assert passes before it fails and cause ICE. Could it be that the additional conditions that are causing it to use lra causing it to fail? I am still continuing to investigate here. Regards, Saurabh=