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 465313858439; Wed, 19 Jul 2023 23:31:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 465313858439
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689809495;
	bh=RtSh2Vrsw4pN4NZUlRQMP/BKIW8BPuAGM1O+5cO+0iY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ACDtsS5FWYFThbZTnrsvvPqLCa4TLV3Uwswm1xXPH4EI/A0zbl7xPXuwHXgTXI/Nh
	 am6vAQUIrjvQVsUtdMtrGQuoTWcj7zCtR/EjHoG6JTbdwPyts9wThRJpYUUp4qMdUg
	 JrILfCOxXrN+g6XrNOKX0TP1BsgDRLHhZdXyppag=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvMTA5OTIxXSBbMTMgUmVncmVzc2lvbl0g?=
 =?UTF-8?B?YysrMTcvZmxvYXRpbmdfZnJvbV9jaGFycy5jYzogY29tcGlsZSBlcnJvcjog?=
 =?UTF-8?B?4oCYZnJvbV9jaGFyc19zdHJ0b2TigJkgd2FzIG5vdCBkZWNsYXJlZCBpbiB0?=
 =?UTF-8?B?aGlzIHNjb3Bl?=
Date: Wed, 19 Jul 2023 23:31:35 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: build
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.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109921-4-G3Fka8V14R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109921-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109921-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=3D109921

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:cd2f934bb09c04e62beb8eb5421467184598983b

commit r13-7593-gcd2f934bb09c04e62beb8eb5421467184598983b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu May 25 10:32:33 2023 +0100

    libstdc++: Fix preprocessor conditions for std::from_chars [PR109921]

    We use the from_chars_strtod function with __strtof128 to read a
    _Float128 value, but from_chars_strtod is not defined unless uselocale
    is available. This can lead to compilation failures for some targets,
    because we try to define the _Float128 overload in terms of a
    non-existing from_chars_strtod function.

    Only try to use __strtof128 if uselocale is available and therefore we
    can use the from_chars_strtod function template.

    This is a simpler change than r14-1431-g7037e7b6e4ac41 on trunk, because
    that caused unwanted ABI regressions (PR libstdc++/110077).

    libstdc++-v3/ChangeLog:

            PR libstdc++/109921
            * src/c++17/floating_from_chars.cc (USE_STRTOF128_FOR_FROM_CHAR=
S):
            Only define when USE_STRTOD_FOR_FROM_CHARS is also defined.
            (USE_STRTOD_FOR_FROM_CHARS): Do not undefine when long double is
            binary64.
            (from_chars(const char*, const char*, double&, chars_format)):
            Check __LDBL_MANT_DIG__ =3D=3D __DBL_MANT_DIG__ here.=