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 r12-9668] [libstdc++] [testsuite] xfail to_chars/long_double on x86-vxworks Date: Tue, 30 May 2023 22:01:08 +0000 (GMT) [thread overview] Message-ID: <20230530220108.352593857707@sourceware.org> (raw) https://gcc.gnu.org/g:b99118d46f4c35c355f99983809cfccc8cd67d7f commit r12-9668-gb99118d46f4c35c355f99983809cfccc8cd67d7f Author: Alexandre Oliva <oliva@adacore.com> Date: Thu May 25 05:57:11 2023 -0300 [libstdc++] [testsuite] xfail to_chars/long_double on x86-vxworks Just as on aarch64, x86's wider long double experiences loss of precision with from_chars implemented in terms of double. Expect the execution fail. for libstdc++-v3/ChangeLog * testsuite/20_util/to_chars/long_double.cc: Expect execution fail on x86-vxworks. (cherry picked from commit 7daa166fe89fca4ff1baa063c00a5a690f7e462f) Diff: --- libstdc++-v3/testsuite/20_util/to_chars/long_double.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 52e382e76a1..01bfec79bb1 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* } } +// { dg-xfail-run-if "from_chars limited to double-precision" { aarch64-*-vxworks* i*86-*-vxworks* } } // { dg-require-effective-target ieee_floats } // { dg-require-effective-target size32plus }
reply other threads:[~2023-05-30 22:01 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=20230530220108.352593857707@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: linkBe 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).