public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH] testsuite: pr59833.c and pr61441.c should use -fsignaling-nans
Date: Thu, 16 Feb 2017 17:47:00 -0000	[thread overview]
Message-ID: <df3cdced97dc60230edd431c77b8190954a451ef.1487168172.git.segher@kernel.crashing.org> (raw)

The testcases pr59833.c and pr61441.c check whether signaling NaNs as
input to some operation result in quiet NaNs.  Without -fsignaling-nans
this is not guaranteed to happen.  So, this patch add this option to
these testcases.

Tested on powerpc64-linux {-m32,-m64}, on aarch64-linux, and on
x86_64-linux (where there is no issignaling, huh -- I tested on gcc20).

Is this okay for trunk?


Segher


2017-02-16  Segher Boessenkool  <seher@kernel.crashing.org>

gcc/testsuite/
	* gcc.dg/pr59833.c: Add -fsignaling-nans to options.
	* gcc.dg/pr61441.c: Ditto.

---
 gcc/testsuite/gcc.dg/pr59833.c | 2 +-
 gcc/testsuite/gcc.dg/pr61441.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/pr59833.c b/gcc/testsuite/gcc.dg/pr59833.c
index 45fcf7f..c75efde 100644
--- a/gcc/testsuite/gcc.dg/pr59833.c
+++ b/gcc/testsuite/gcc.dg/pr59833.c
@@ -1,5 +1,5 @@
 /* { dg-do run { target { *-*-linux* *-*-gnu* } } } */
-/* { dg-options "-O0 -lm" } */
+/* { dg-options "-O0 -lm -fsignaling-nans" } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target issignaling } */
 
diff --git a/gcc/testsuite/gcc.dg/pr61441.c b/gcc/testsuite/gcc.dg/pr61441.c
index 1b0f181..9408e85 100644
--- a/gcc/testsuite/gcc.dg/pr61441.c
+++ b/gcc/testsuite/gcc.dg/pr61441.c
@@ -1,5 +1,5 @@
 /* { dg-do run { target { *-*-linux* *-*-gnu* } } } */
-/* { dg-options "-O1 -lm -fexcess-precision=standard" } */
+/* { dg-options "-O1 -lm -fexcess-precision=standard -fsignaling-nans" } */
 /* { dg-require-effective-target issignaling } */
 
 #define _GNU_SOURCE
-- 
1.9.3

             reply	other threads:[~2017-02-16 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 17:47 Segher Boessenkool [this message]
2017-02-16 23:13 ` Jeff Law
2017-02-20 19:30 ` Jakub Jelinek
2017-02-20 20:35   ` Jakub Jelinek

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=df3cdced97dc60230edd431c77b8190954a451ef.1487168172.git.segher@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@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).