public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: "Franथईois-Xavier Coudert" <fxcoudert@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-6517] Fortran: fix testcase compiler flags Date: Wed, 12 Jan 2022 10:22:08 +0000 (GMT) [thread overview] Message-ID: <20220112102208.C736B3858001@sourceware.org> (raw) https://gcc.gnu.org/g:6b14100b9504800768da726dcb81f1857db3b493 commit r12-6517-g6b14100b9504800768da726dcb81f1857db3b493 Author: Francois-Xavier Coudert <fxcoudert@gmail.com> Date: Wed Jan 12 11:19:37 2022 +0100 Fortran: fix testcase compiler flags -fsignaling-nans is already passed by ieee.exp, so it's not needed. We must use dg-additional-options instead of dg-options, otherwise we override flags passed from ieee.exp. And we need to use -w because some options only make sense for the Fortran source. gcc/testsuite/ChangeLog: * gfortran.dg/ieee/signaling_1.f90: Adjust flags. Diff: --- gcc/testsuite/gfortran.dg/ieee/signaling_1.f90 | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90 b/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90 index a1403e6ce16..3d846fc1038 100644 --- a/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90 +++ b/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90 @@ -1,7 +1,9 @@ ! { dg-do run } ! { dg-require-effective-target issignaling } */ ! { dg-additional-sources signaling_1_c.c } -! { dg-options "-fsignaling-nans" } +! { dg-additional-options "-w" } +! the -w option is needed to make f951 not report a warning for +! the -fintrinsic-modules-path option passed by ieee.exp ! program test use, intrinsic :: iso_c_binding
reply other threads:[~2022-01-12 10:22 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=20220112102208.C736B3858001@sourceware.org \ --to=fxcoudert@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).