From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 646713858C31; Fri,  8 Mar 2024 11:01:20 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 646713858C31
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709895680;
	bh=PNiWGVAVeXBCRXJsjmEbieAPRMULKS5WK3Q8Wjvp7sc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QfEJwyGDHdJSIapPaxfDdwqS3GJ79IXCs2bSqOfqOvkp+Ypyoo4sVgwFgju8jcAco
	 figQCdmIOUdk2RAM+K1z6kB4l70ygRFjMGiYDsuTFwqpbA5Q7lP4bf89t/lmKkLkBO
	 IdONmXhl0ceWrzi+qQCp2tW1fAoxXo6qcmIuK6H8=
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114137] ICE when building lua-5.4.6 with
 -fharden-control-flow-redundancy on x86 (error: invalid rtl sharing found in
 the insn)
Date: Fri, 08 Mar 2024 11:01:18 +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-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: <bug-114137-4-DhZRiRChL1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114137-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114137-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #6 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
Thanks for the report.

Something's very rotten here.  cfrvisited is an automatic variable, why oh =
why
would we have GOTOFF unspecs for it?!?

I'd be interested in a preprocessed testcase that will trigger the problem.

Failing that, I suppose I could try to drive a remote debug session if you'=
re
up for it.  If it is indeed something related with GC as suggested (and it
sounds plausible), the exact details of when it hits will depend on local
hardware details and not necessarily carry over to other machines.=