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] xfail fp-uint64-convert-double tests
Date: Thu,  1 Dec 2022 07:40:13 +0000 (GMT)	[thread overview]
Message-ID: <20221201074013.6E7133856975@sourceware.org> (raw)

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

commit e95ac2c3c3db989a00d58aebb0568468be46bafa
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Dec 1 04:38:49 2022 -0300

    [arm] xfail fp-uint64-convert-double tests
    
    The FP emulation on ARM doesn't take rounding modes into account.  The
    tests require hard_float, but that only tests for calls when adding
    doubles.  There are arm targets that support hardware adds, but that
    emulate conversions.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/torture/fp-uint64-convert-double-1.c: Expect fail on
            arm-*-eabi*.
            * gcc.dg/torture/fp-uint64-convert-double-2.c: Likewise.
    
    Change-Id: I9c559a7c4d4227165a8b3d18e9f8fc88af1e4134
    TN: VB12-013

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 0c7bf003e93..61cfa963746 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 } */
+/* { dg-do run { xfail { arm-*-eabi* } } } */
 /* { 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 ac24b351a46..b32b28a3295 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 } */
+/* { dg-do run { xfail { arm-*-eabi* } } } */
 /* { dg-require-effective-target fenv } */
 /* { dg-require-effective-target hard_float } */
 /* { dg-additional-options "-frounding-math" } */

             reply	other threads:[~2022-12-01  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  7:40 Alexandre Oliva [this message]
2022-12-03  7:33 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=20221201074013.6E7133856975@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).