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 7C0463858D39; Tue, 14 Mar 2023 17:22:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7C0463858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678814572;
	bh=wd3d+Uq5YneoSM/logcukpMXJalhtrAcVAgTfPL4uYU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=IORyiH5jDvTr82F4uFDEPMXgD7+NVcXBRN6R0Xi0hxjNjo3iTsvkRazZabDt84slo
	 ZAlUESFK7PdyLgtMGZg5drbK7XNoyJIALrltIfH782rbyz/yo6nlIs9GsoWjUVAfes
	 QtoZ/HlUr+vdMvmSeCtILWJ+GgEQwQBwC3t5Rpdg=
From: "tstellar at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc
 after upgrading from gcc 12.2.1 to 13.0.1 since r13-2706-g6e80a1d164d1f9
Date: Tue, 14 Mar 2023 17:22:51 +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: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tstellar at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
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-108994-4-HScMVYYGiZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108994-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=3D108994

--- Comment #19 from Tom Stellard <tstellar at redhat dot com> ---
Thanks, Jakub.  It looks like this is in fact an LLVM bug.  I've posted a p=
atch
here that fixes my test case: https://reviews.llvm.org/D146067=