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 678733857C42; Wed, 28 Sep 2022 18:47:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 678733857C42
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664390859;
	bh=u1aInZ5zXOZmetSwd1keXTH/2JXwTQ1Hm3Kn/V0W2Cc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XueHk3TLostudJwXHCBjBlEyDRk9s/99j+mEH8DHa+glwWCQYW2xEq9PbRRd4qopU
	 2zZmX7Q/wsVRKmihudWAdL45qff0Ld8CTdFCHwZ3cr/s5zDEzdTs1GDpGd4Zg11scK
	 L4LofnGLeyKeBosZYWoQ4LsU35vrl8RITEeR4PpQ=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107059] [13 regression] bootstrap failure after
 r13-2887-gb04208895fed34
Date: Wed, 28 Sep 2022 18:47:39 +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: jakub at gcc dot gnu.org
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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107059-4-aQj5ctJbSC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107059-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=3D107059

--- Comment #24 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #22)
> Even with the fixincluded headers properly being used, the powerpc64le=20
> issue still applies because of the issue I noted in=20
> https://sourceware.org/pipermail/libc-alpha/2022-September/142259.html=20
> with certain required changes to the powerpc version of bits/floatn.h not=
=20
> being covered by the fixincludes fixes added.  You get errors such as:
>=20
> /scratch/jmyers/glibc-bot/build/compilers/powerpc64le-linux-gnu/gcc/gcc/
> include-fixed/bits/floatn.h:88:9: error: multiple types in one declaration
>    88 | typedef __float128 _Float128;
>       |         ^~~~~~~~~~
>=20
> while building libstdc++.  (Whereas other architectures can build GCC OK=
=20
> but then run into failures building glibc that my glibc patch is intended=
=20
> to address.)

Posted patch for this in
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602431.html=