public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
	"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: testsuite: use cmath long double overloads
Date: Mon, 27 Jun 2022 12:01:35 +0100	[thread overview]
Message-ID: <CACb0b4=ap19erUkU6W=XBZrWebgGTOW_bOWRXYbH7d5nrWMW9w@mail.gmail.com> (raw)
In-Reply-To: <ork09aefuy.fsf@lxoliva.fsfla.org>

On Tue, 21 Jun 2022 at 06:39, Alexandre Oliva via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
>
> 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.
>
> Regstrapped on x86_64-linux-gnu, also tested with a cross to
> aarch64-rtems6.  Ok to install?

OK


>
>
> for  libstdc++-v3/ChangeLog
>
>         * testsuite/20_util/to_chars/long_double.cc: Use cmath
>         long double overloads for nexttoward and ldexp.
> ---
>  .../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 0b1c2c2936fdc..498388110b179 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;
>
>
> --
> Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
>    Free Software Activist                       GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts.  Ask me about <https://stallmansupport.org>
>


      parent reply	other threads:[~2022-06-27 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  5:37 Alexandre Oliva
2022-06-27 10:19 ` Alexandre Oliva
2022-06-27 11:01 ` Jonathan Wakely [this message]

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='CACb0b4=ap19erUkU6W=XBZrWebgGTOW_bOWRXYbH7d5nrWMW9w@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=oliva@adacore.com \
    /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).