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 5B8B4385DC1F; Fri,  7 Oct 2022 07:00:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5B8B4385DC1F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665126027;
	bh=9eyKglAb5b3qduM9LoRiNdAKrJ+RlUctcPFjAhM0KAI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hFzvvFRyGSpz4JvLUfrGVg89UI5wAguVmqJW2r/pGZchxp6Yo+hRYfcyeUgbP+SOT
	 C4pEQ1sJTDBhFda0bbwZnvmz+0LWA0vN5F9A8iKv9zAvPMNjGG08ux7l+zpkW66RIm
	 KYhlS4CaOLRXaBI6ULapRO02P6P/YLl88A2xKahA=
From: "cvs-commit 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: Fri, 07 Oct 2022 07:00:27 +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: cvs-commit 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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107059-4-ezMA3LzDqa@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 #33 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:348e46fa8cba960c23170673bfc0c1b4fb384975

commit r13-3148-g348e46fa8cba960c23170673bfc0c1b4fb384975
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Oct 7 08:59:05 2022 +0200

    fixincludes: Deal also with the _Float128x cases [PR107059]

    On Wed, Sep 28, 2022 at 08:19:43PM +0200, Jakub Jelinek via Gcc-patches
wrote:
    > Another case are the following 3 snippets:
    > #  if !__GNUC_PREREQ (7, 0) || defined __cplusplus
    > #   error "_Float128X supported but no constant suffix"
    > #  else
    > #   define __f128x(x) x##f128x
    > #  endif
    > ...
    > #  if !__GNUC_PREREQ (7, 0) || defined __cplusplus
    > #   error "_Float128X supported but no complex type"
    > #  else
    > #   define __CFLOAT128X _Complex _Float128x
    > #  endif
    > ...
    > #  if !__GNUC_PREREQ (7, 0) || defined __cplusplus
    > #   error "_Float128x supported but no type"
    > #  endif
    > but as no target has _Float128x right now and don't see it
    > coming soon, it isn't a big deal (on the glibc side it is of
    > course ok to adjust those).

    This incremental patch deals handles the above 3 cases, so we
    fixinclude what glibc itself changed too.

    2022-10-07  Jakub Jelinek  <jakub@redhat.com>

            PR bootstrap/107059
            * inclhack.def (glibc_cxx_floatn_5): New.
            * fixincl.x: Regenerated.
            * tests/base/bits/floatn.h: Regenerated.=