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 2C41D3858C60; Fri,  3 Mar 2023 08:45:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2C41D3858C60
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677833126;
	bh=h1xNeHe3/shEz4pVFPhM0L8rBYi/BCPv+uVSze5RCZM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=upjEZZHk9nN2fWPFtHV55PFu448FANRVN1/m8aNP8SpQFF3sSsvH/j9+PgsYDSPM1
	 WelOfJndw8uj+g4+HtD0Fm+T+qA7EUk+RvL73SHyszJIsMADXemPVchyP4MR+Gr5dH
	 t3yEWJlGYz0ql/YDkDAkeFUtcHZpUdUgiqBvemYg=
From: "jakub at gcc dot gnu.org" <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
Date: Fri, 03 Mar 2023 08:45:25 +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: jakub 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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-108994-4-sPshrOgICX@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd start with verification if it is really libgcc, so don't recompile the =
app,
just try it against GCC 12.2.1 libgcc vs. 13.0.1.  If it is libgcc, then th=
ere
are other revisions to suspect, like
r13-2706-g6e80a1d164d1f9
r13-4757-g1c118c99706001
r13-4758-g6e56633daae79f
beyond what Andrew wrote.  And, for libgcc you don't really need to rebuild=
 the
whole thing, once you build once (perhaps with the flags Jonathan mentioned=
),
git reset --hard some-commit you can just cd aarch64*/libgcc; make -jN and
retry.=