From: Jonathan Wakely <jwakely.gcc@gmail.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] xfail double-prec from_chars for x86_64 ldbl
Date: Tue, 30 May 2023 08:11:33 +0100 [thread overview]
Message-ID: <CAH6eHdQpx8nsQe1+tNOW8OMx7-NUgTcdp6ZqFJDkFAfTnBBFQw@mail.gmail.com> (raw)
In-Reply-To: <orr0qy5tdy.fsf@lxoliva.fsfla.org>
[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]
On Tue, 30 May 2023, 05:35 Alexandre Oliva via Libstdc++, <
libstdc++@gcc.gnu.org> wrote:
>
> When long double is wider than double, but from_chars is implemented
> in terms of double, tests that involve the full precision of long
> double are expected to fail. Mark them as such on x86_64-*-vxworks*.
>
OK for trunk/13/12
> Tested on x86_64-vxworks7r2 with gcc-12. Ok to install?
>
>
> for libstdc++-v3/ChangeLog
>
> * testsuite/20_util/from_chars/4.cc: Skip long double test06
> on x86_64-vxworks.
> * testsuite/20_util/to_chars/long_double.cc: Xfail run on
> x86_64-vxworks.
> ---
> libstdc++-v3/testsuite/20_util/from_chars/4.cc | 2 +-
> .../testsuite/20_util/to_chars/long_double.cc | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libstdc++-v3/testsuite/20_util/from_chars/4.cc
> b/libstdc++-v3/testsuite/20_util/from_chars/4.cc
> index c3594f9014bd3..63a32b511be4e 100644
> --- a/libstdc++-v3/testsuite/20_util/from_chars/4.cc
> +++ b/libstdc++-v3/testsuite/20_util/from_chars/4.cc
> @@ -18,7 +18,7 @@
> // <charconv> is supported in C++14 as a GNU extension
> // { dg-do run { target c++14 } }
> // { dg-add-options ieee }
> -// { dg-additional-options "-DSKIP_LONG_DOUBLE" { target
> aarch64-*-vxworks* } }
> +// { dg-additional-options "-DSKIP_LONG_DOUBLE" { target
> aarch64-*-vxworks* x86_64-*-vxworks* } }
>
> #include <charconv>
> #include <string>
> 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 08363d9d04003..df02dff935f40 100644
> --- a/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc
> +++ b/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc
> @@ -36,7 +36,7 @@
>
> // On systems that use double-precision from_chars for long double,
> // this is expected to fail.
> -// { dg-xfail-run-if "from_chars limited to double-precision" {
> aarch64-*-vxworks* i*86-*-vxworks* } }
> +// { dg-xfail-run-if "from_chars limited to double-precision" {
> aarch64-*-vxworks* i*86-*-vxworks* x86_64-*-vxworks* } }
>
> // { dg-require-effective-target ieee_floats }
> // { dg-require-effective-target size32plus }
>
>
> --
> 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>
>
prev parent reply other threads:[~2023-05-30 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 4:35 Alexandre Oliva
2023-05-30 7:11 ` 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=CAH6eHdQpx8nsQe1+tNOW8OMx7-NUgTcdp6ZqFJDkFAfTnBBFQw@mail.gmail.com \
--to=jwakely.gcc@gmail.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).