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 r14-1878] [libstdc++] [testsuite] xfail dbl from_chars for aarch64 rtems ldbl
Date: Fri, 16 Jun 2023 06:41:56 +0000 (GMT)	[thread overview]
Message-ID: <20230616064156.494E93853D05@sourceware.org> (raw)

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

commit r14-1878-ga371a639b76f1bdcd7a957f400b5a7c0faf30a15
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Fri Jun 16 03:23:47 2023 -0300

    [libstdc++] [testsuite] xfail dbl from_chars for aarch64 rtems ldbl
    
    rtems, like vxworks, uses fast-float doubles for from_chars even for
    long double, so it loses precision, so expect the long double bits to
    fail on aarch64.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/20_util/from_chars/4.cc: Skip long double on
            aarch64-rtems.

Diff:
---
 libstdc++-v3/testsuite/20_util/from_chars/4.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/20_util/from_chars/4.cc b/libstdc++-v3/testsuite/20_util/from_chars/4.cc
index 206e18daeb2..76e07df9d2b 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* x86_64-*-vxworks* } }
+// { dg-additional-options "-DSKIP_LONG_DOUBLE" { target aarch64-*-rtems* aarch64-*-vxworks* x86_64-*-vxworks* } }
 
 #include <charconv>
 #include <string>

                 reply	other threads:[~2023-06-16  6:41 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=20230616064156.494E93853D05@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).