public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110957] New: -ffpe-trap and -ffpe-summary options issues
Date: Wed, 09 Aug 2023 09:28:41 +0000 [thread overview]
Message-ID: <bug-110957-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110957
Bug ID: 110957
Summary: -ffpe-trap and -ffpe-summary options issues
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: ubizjak at gmail dot com
Target Milestone: ---
A couple of issues with -ffpe-trap and -ffpe-summary options:
a) Invalid argument report should be switched:
$ gfortran -ffpe-summary=aaa ac.f90
f951: Fatal Error: Argument to ‘-ffpe-trap’ is not valid: aaa
compilation terminated.
$ gfortran -ffpe-trap=aaa ac.f90
f951: Fatal Error: Argument to ‘-ffpe-summary’ is not valid: aaa
compilation terminated.
b) Specifying also -fno-trapping-math should be detected and handled
$ gfortran -ffpe-trap=invalid -fno-trapping-math ac.f90
[no diagnostics]
The issue b) should either report incompatibility between options, or force
-ftrapping-math (probably with a warning). Ideally, -ffpe-* should always set
flag_trapping_math, in case the compiler switches to no trapping math by
default in future.
next reply other threads:[~2023-08-09 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 9:28 ubizjak at gmail dot com [this message]
2023-08-13 20:19 ` [Bug fortran/110957] " anlauf at gcc dot gnu.org
2023-10-06 20:19 ` 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@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: 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).