public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110957] -ffpe-trap and -ffpe-summary options issues Date: Sun, 13 Aug 2023 20:19:34 +0000 [thread overview] Message-ID: <bug-110957-4-soPnwKjtdV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110957-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110957 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2023-08-13 --- Comment #1 from anlauf at gcc dot gnu.org --- Confirmed (a). Obvious fix: diff --git a/gcc/fortran/options.cc b/gcc/fortran/options.cc index 27311961325..2d4be853c66 100644 --- a/gcc/fortran/options.cc +++ b/gcc/fortran/options.cc @@ -586,7 +586,7 @@ gfc_handle_fpe_option (const char *arg, bool trap) break; } } - if (!result && !trap) + if (!result && trap) gfc_fatal_error ("Argument to %<-ffpe-trap%> is not valid: %s", arg); else if (!result) gfc_fatal_error ("Argument to %<-ffpe-summary%> is not valid: %s", arg); Regarding (b), the gfortran manual says: -ffpe-summary=list list can be either ‘none’, ‘all’ or a comma-separated list ... -ffpe-trap=list list is a (possibly empty) comma-separated list ... Unfortunately, 'none' is not accepted for list here, but might be handy. Need to check where the options conflict can be diagnosed.
next prev parent reply other threads:[~2023-08-13 20:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-09 9:28 [Bug fortran/110957] New: " ubizjak at gmail dot com 2023-08-13 20:19 ` anlauf at gcc dot gnu.org [this message] 2023-10-06 20:19 ` [Bug fortran/110957] " anlauf at gcc dot gnu.org 2023-10-13 20:07 ` cvs-commit at gcc dot gnu.org
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=bug-110957-4-soPnwKjtdV@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).