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 8CAF238582B0; Tue, 25 Oct 2022 07:00:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8CAF238582B0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666681233;
	bh=S5mASVlEzFzBkQ7KomNNycixxEM/8pelLP2nhhakUTE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=opkJ594oWsuc1ApuA4Gh21jaTIN/dWcOEDXpO8Gm1njVPeokiIJz5K+h6SI1A/Sv6
	 v1xAlzUYASvioGVBddSnox3erGe2SdoHOnmi/Vh/+V8gCWlLtA0p0LVMDyb/LkWIGH
	 Hi/JEDgXb+4ZoYnZ5SEZCVVvUgcX1CDMJe/vCnb0=
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107353] [13 regression] Numerous ICEs after
 r13-3416-g1d561e1851c466
Date: Tue, 25 Oct 2022 07:00:32 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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: 
Message-ID: <bug-107353-4-O2GZFuKeVA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107353-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107353-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=3D107353

--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #7)
> I have it on x86_64-pc-linux-gnu=E2=80=A6

Thanks for the info (I assume you don't have any special configure argument=
s),
but that's surprising, I ran bootstrap+regtest before committing the patch,=
 and
did not see such issues. I'll recheck with today's trunk.=