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)] xfail fp-uint64-convert-double-* on all arm targets
Date: Wed, 22 Feb 2023 14:49:28 +0000 (GMT)	[thread overview]
Message-ID: <20230222144928.2F4173858431@sourceware.org> (raw)

https://gcc.gnu.org/g:3439cccf89739e45d071826fd864ed221cb7a22a

commit 3439cccf89739e45d071826fd864ed221cb7a22a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Feb 16 06:39:39 2023 -0300

    xfail fp-uint64-convert-double-* on all arm targets
    
    It wasn't long ago that I xfailed these tests on arm-*-eabi, but the
    fail is expected on all other arm targets: even when hard float is
    available, conversions between 64-bit integers and double are always
    emulated on ARM, and the emulation disregards rounding modes.  So,
    bump the xfail to all of arm-*-*.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/torture/fp-uint64-convert-double-1.c: XFAIL on all of
            arm-*-*.
            * gcc.dg/torture/fp-uint64-convert-double-2.c: Likewise.

Diff:
---
 gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-1.c | 2 +-
 gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-2.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-1.c b/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-1.c
index 61cfa963746..8f437e2efb1 100644
--- a/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-1.c
+++ b/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-1.c
@@ -1,5 +1,5 @@
 /* PR84407 */
-/* { dg-do run { xfail { arm-*-eabi* } } } */
+/* { dg-do run { xfail { arm-*-* } } } */
 /* { dg-require-effective-target fenv } */
 /* { dg-require-effective-target hard_float } */
 /* { dg-additional-options "-frounding-math -fexcess-precision=standard" } */
diff --git a/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-2.c b/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-2.c
index b32b28a3295..fd3f4cbfb83 100644
--- a/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-2.c
+++ b/gcc/testsuite/gcc.dg/torture/fp-uint64-convert-double-2.c
@@ -1,5 +1,5 @@
 /* PR84407 */
-/* { dg-do run { xfail { arm-*-eabi* } } } */
+/* { dg-do run { xfail { arm-*-* } } } */
 /* { dg-require-effective-target fenv } */
 /* { dg-require-effective-target hard_float } */
 /* { dg-additional-options "-frounding-math" } */

             reply	other threads:[~2023-02-22 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 14:49 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-23 13:48 Alexandre Oliva
2023-02-22 17:23 Alexandre Oliva
2023-02-16 11:12 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=20230222144928.2F4173858431@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: 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).