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 01DAE3858D37; Mon, 10 Oct 2022 04:37:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 01DAE3858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665376642;
	bh=dOFqnwx6Um+ZbdTjKtfq+oRM6rwbg+XkXsApcSs9kBo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lHCGifIEwGl4RAYWx79PKdudqaUryMkwxZzig8gOouHRNxqv43hkdweFz0y8ND/7A
	 vcynvGJjrGPwNHqdXlgtmv5q5mH20nt9zK5lHjw5uM50cxQimDEaB6bE6fmGuH98x7
	 9htDyWTEm8/jqxvbRcaH34socG7OJBJP/nk77A/0=
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107120] [13 Regression] trunk fails to bootstrap on
 powerpc64le-linux-gnu
Date: Mon, 10 Oct 2022 04:37:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx 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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107120-4-8lyS6lJbrN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107120-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107120-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=3D107120

--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Arseny Solokha from comment #2)
> I get the same bootstrap error in libitm while building gcc 13.0.0 202210=
02
> snapshot (g:d01bd0b0f3b8f4c33c437ff10f0b949200627f56) against glibc 2.36 =
for
> x86_64.

Jakub in PR107128 comment 4 said enough to resolve this issue for me.=