public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: use cmath long double overloads
Date: Thu, 23 Jun 2022 07:15:25 +0000 (GMT)	[thread overview]
Message-ID: <20220623071525.6C19B3834F39@sourceware.org> (raw)

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

commit a4702b18e5ce8894b7c845b9097278323b4196f2
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 19:43:42 2022 -0300

    libstdc++: testsuite: use cmath long double overloads
    
    In case we need to supplement the C standard library with additional
    definitions for float and long double, the declarations expected to be
    in the C headers may not be there.  Rely on the cmath overloads
    instead.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/20_util/to_chars/long_double.cc: Use cmath
            long double overloads for nexttoward and ldexp.

Diff:
---
 libstdc++-v3/testsuite/20_util/to_chars/long_double.cc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc b/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc
index 0b1c2c2936f..498388110b1 100644
--- a/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc
+++ b/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc
@@ -54,11 +54,11 @@ namespace detail
 {
   long double
   nextupl(long double x)
-  { return nexttowardl(x, numeric_limits<long double>::infinity()); }
+  { return nexttoward(x, numeric_limits<long double>::infinity()); }
 
   long double
   nextdownl(long double x)
-  { return nexttowardl(x, -numeric_limits<long double>::infinity()); }
+  { return nexttoward(x, -numeric_limits<long double>::infinity()); }
 }
 
 // The long double overloads of std::to_chars currently just go through printf
@@ -138,7 +138,7 @@ test01()
   for (int exponent : {-11000, -3000, -300, -50, -7, 0, 7, 50, 300, 3000, 11000})
     for (long double testcase : hex_testcases)
       {
-	testcase = ldexpl(testcase, exponent);
+	testcase = ldexp(testcase, exponent);
 	if (testcase == 0.0L || isinf(testcase))
 	  continue;


             reply	other threads:[~2022-06-23  7:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  7:15 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-27 10:51 Alexandre Oliva
2022-06-27  9:33 Alexandre Oliva
2022-06-23 12:44 Alexandre Oliva
2022-06-23 12:29 Alexandre Oliva
2022-06-23 12:22 Alexandre Oliva
2022-06-23 10:05 Alexandre Oliva
2022-06-22  5:22 Alexandre Oliva
2022-06-21  0:15 Alexandre Oliva
2022-06-21  0:07 Alexandre Oliva

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=20220623071525.6C19B3834F39@sourceware.org \
    --to=aoliva@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).