public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: testsuite: use cmath long double overloads
Date: Mon, 27 Jun 2022 07:19:56 -0300	[thread overview]
Message-ID: <or7d52z9v7.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <ork09aefuy.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Tue, 21 Jun 2022 02:37:57 -0300")

On Jun 21, 2022, Alexandre Oliva <oliva@adacore.com> wrote:

> 	* testsuite/20_util/to_chars/long_double.cc: Use cmath
> 	long double overloads for nexttoward and ldexp.

Ping?

https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596921.html

-- 
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>

  reply	other threads:[~2022-06-27 10:20 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 [this message]
2022-06-27 11:01 ` Jonathan Wakely

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=or7d52z9v7.fsf@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).