public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] [arm] [vxworks] xfail fp-double-convert-float-1.c Date: Thu, 16 Feb 2023 11:13:42 +0000 (GMT) [thread overview] Message-ID: <20230216111342.0CC083857C55@sourceware.org> (raw) https://gcc.gnu.org/g:1d816abbae684c2ef0082c15d37953fc78058bfc commit 1d816abbae684c2ef0082c15d37953fc78058bfc Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Feb 16 07:45:36 2023 -0300 [arm] [vxworks] xfail fp-double-convert-float-1.c Even with vcvt.f32.f64, the FE_UPWARD test rounds down and fails. I'm not sure whether this opcode disregards the rounding mode (it looks like it should take it into account) or it is a qemu bug, but it does not look like GCC is doing anything wrong, and the test fails, so I'm marking the fail as expected on arm-*-vxworks*. for gcc/testsuite/ChangeLog * gcc.dg/torture/fp-double-convert-float-1.c: XFAIL on arm-*-vxworks*. Diff: --- gcc/testsuite/gcc.dg/torture/fp-double-convert-float-1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/torture/fp-double-convert-float-1.c b/gcc/testsuite/gcc.dg/torture/fp-double-convert-float-1.c index 1c28a9e101e..c3ca69d64bb 100644 --- a/gcc/testsuite/gcc.dg/torture/fp-double-convert-float-1.c +++ b/gcc/testsuite/gcc.dg/torture/fp-double-convert-float-1.c @@ -1,5 +1,5 @@ /* PR57245 */ -/* { dg-do run } */ +/* { dg-do run { xfail { arm-*-vxworks* } } } */ /* { dg-require-effective-target fenv } */ /* { dg-require-effective-target hard_float } */ /* { dg-additional-options "-frounding-math" } */
next reply other threads:[~2023-02-16 11:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-16 11:13 Alexandre Oliva [this message] 2023-02-23 13:27 Alexandre Oliva 2023-02-23 13:49 Alexandre Oliva 2023-02-23 13:57 Alexandre Oliva 2023-02-23 14:02 Alexandre Oliva
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=20230216111342.0CC083857C55@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-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).