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 61BD93858C27; Tue, 22 Nov 2022 14:28:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 61BD93858C27
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669127290;
	bh=D1S8l9wCCl926gM1OntcI3gypKOtr5BgNn0Zo/3PgPY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=oZOyx3xeOVNa5bsh6bGQGs4Kh2vYYdQ588VB5odnCBuG9MAT14CPJ4/s31hCTx7tu
	 OYyQl29ztDvR3xPS0sgigkvm31ZU55tZVwOBMRZA6EFYpaWzPjwjuhuG/n1C9wVXOH
	 XOVzo9fJcT7We+gFXfXqVGOUtHqoe8KLJB9NvR8I=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs
Date: Tue, 22 Nov 2022 14:28:02 +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.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-107815-4-LBLXFUSPJX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107815-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=3D107815

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can you please uncomment the
//    std::cout << i << ' ' << std::string_view (str1, ptr1) << '\n';
and
//    std::cout << i << ' ' << std::string_view (str1, ptr5) << '\n';
lines in the test, so that it is clear at least which test it is on?
If line 66 fails, it is a fixed printing test trying to verify
that the string created by line 60 was actually the minimal.
On SPARC Solaris, I assume long double is IEEE quad, and it is the shortest
version, so should use ryu library for both cases.
Line 74 failure is about whether the created string can be read back,
in that case for IEEE quad fast_float library can't be used and so it should
use newlocale/uselocale/strtold/uselocale/freelocale, or if the OS doesn't
support newlocale/uselocale/freelocale most likely just strtod with lost
precision (so in that case the test would fail) on line 74.=