public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-4108] libstdc++: Disable std::format of _Float128 if std::to_chars is innaccurate
Date: Wed, 16 Nov 2022 20:59:27 +0000 (GMT)	[thread overview]
Message-ID: <20221116205927.2AB9B396D83B@sourceware.org> (raw)

https://gcc.gnu.org/g:22cb0fea718fd4dab8c97c8f03054a2fb7dc3d76

commit r13-4108-g22cb0fea718fd4dab8c97c8f03054a2fb7dc3d76
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Nov 15 15:31:17 2022 +0000

    libstdc++: Disable std::format of _Float128 if std::to_chars is innaccurate
    
    This restricts std::format support for _Float128 (and __float128) to
    targets where glibc provides __strfromf128 and so can give correct
    output.
    
    libstdc++-v3/ChangeLog:
    
            * include/std/format [__FLT128_DIG__] (_GLIBCXX_FORMAT_F128):
            Only support formatting _Float128 when glibc provides the
            functionality needed for accurate std::to_chars.

Diff:
---
 libstdc++-v3/include/std/format | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/include/std/format b/libstdc++-v3/include/std/format
index 204a1710aca..fb29f7e7835 100644
--- a/libstdc++-v3/include/std/format
+++ b/libstdc++-v3/include/std/format
@@ -1235,13 +1235,13 @@ namespace __format
   using __float128_t = long double;
 # define _GLIBCXX_FORMAT_F128 1
 
-#elif __FLT128_DIG__ && defined(__GLIBC_PREREQ) // see floating_to_chars.cc
+#elif __FLT128_DIG__ && defined(_GLIBCXX_HAVE_FLOAT128_MATH)
 
   // Format 128-bit floating-point types using _Float128.
   using __float128_t = _Float128;
 # define _GLIBCXX_FORMAT_F128 2
 
-# if __cplusplus == 202002L || !defined(_GLIBCXX_HAVE_FLOAT128_MATH)
+# if __cplusplus == 202002L
   // These overloads exist in the library, but are not declared for C++20.
   // Make them available as std::__format::to_chars.
   to_chars_result

                 reply	other threads:[~2022-11-16 20:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221116205927.2AB9B396D83B@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).