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 B85DB3857033; Wed, 19 Jul 2023 22:43:11 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B85DB3857033
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689806591;
	bh=QGFvxbgi/p9gx73r3wrSUEckgL8mq02KWG6iwS9FExE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=GuhALMYu3Nk5UzlqRCiimnNKL+CbMJ+wOsZFoprrVNOd7dyNaMZEIoZS0nAz2nJoD
	 N5Al80tS3w4gAbLKOJzbXIdJ53gdZna7vWSHKc1SCcft9X7oDgmRfLNkPmdWvHBF9m
	 a1OL+PiECQOYNgPZV7HKTJnIYJV7AXVXiRKuJy2c=
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 22:43:11 +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-Hv7fQmbPEf@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 #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:0867d30a68de68f4c809757348447bef94ef1491

commit r14-2661-g0867d30a68de68f4c809757348447bef94ef1491
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Jul 19 21:15:17 2023 +0100

    libstdc++: Do not define inaccurate from_chars for _Float128 [PR110077]

    I think r14-1431-g7037e7b6e4ac41 was wrong to try to define the
    _Float128 overload unconditionally. Not all targets need it, so defining
    the lossy fallback using long double is not useful (and caused an ABI
    change on Solaris x86).

    Making the definition depend on USE_STRTOF128_FOR_FROM_CHARS again
    partially reverts the change for PR 109921, however that should still be
    fixed because the changes to make USE_STRTOF128_FOR_FROM_CHARS depend on
    USE_STRTOD_FOR_FROM_CHARS are not reverted.

    libstdc++-v3/ChangeLog:

            PR libstdc++/110077
            * src/c++17/floating_from_chars.cc (from_chars): Only define
            _Float128 overload when using __strfromf128.=