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 9A883385AC2A; Sat, 10 Sep 2022 17:28:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A883385AC2A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1662830924;
	bh=GuYRjcuBwV/QGaU7bgu5Um45QwZjtzAa/htBj93ZFzw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hXv58qeq3dMffo/lBGD60VvXsQDNMJPYJP4SD6bZSLRw5A/G7OXXuEvP3H1Q2vQ1D
	 Hx10VC0b5G4aJ9FhNUff53OiHPe2PclxF8Sgr4dvKXIlLhOWVf0rR0+NrtVg1FIcN5
	 La4oujhEVI8lv3JJwCgLFfETnj01du7GrbXl9m6M=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106652] [C++23] P1467 - Extended floating-point types and
 standard names
Date: Sat, 10 Sep 2022 17:28:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-106652-4-ezkmEx8swR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106652-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=3D106652

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 53559
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D53559&action=3Dedit
gcc13-pr106652-lib.patch

Some unfinished library changes.

Unfortunately, we seem to have a major problem with glibc.
<bits/floatn.h> included from <math.h> etc. on some arches does:
# if __HAVE_FLOAT128

/* The type _Float128 exists only since GCC 7.0.  */
#  if !__GNUC_PREREQ (7, 0) || defined __cplusplus
typedef __float128 _Float128;
#  endif
...
#endif
or
typedef long double _Float128;
etc.
I'm afraid we'll need to fixincludes that and change in glibc.
The question is to what exactly.  I think with the compiler patch _Float<N>
are in C++ generally available as keyword but __STDCPP_FLOAT<N>_T__ that the
libstdc++ patch is using is only defined for C++23.  The F<N> or f<N> liter=
al
suffixes pedwarn before C++23 but bet not in system headers, so glibc then
could use those for C++ always for __GNUC_PREREQ (13, 0)?=