public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102145] TKR mismatches with -pedantic: -fallow-argument-mismatch does not degrade errors to warnings
Date: Tue, 31 Aug 2021 17:24:58 +0000 [thread overview]
Message-ID: <bug-102145-4-wP3aDnKEQ0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102145-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
CC| |kargl at gcc dot gnu.org
Priority|P3 |P5
--- Comment #1 from kargl at gcc dot gnu.org ---
Bummer.
I do note that the gcc.info description describes -pedantic
in terms of only ISO C/C++, but let's assume -pedantic
should apply to ISO Fortran as well. From the gcc manual
-Wpedantic'
'-pedantic'
Issue all the warnings demanded by strict ISO C and ISO C++; reject
all programs that use forbidden extensions, ...
>From Fortran 2018, 4.2 Conformance
A processor conforms to this document if:
...
(10) it contains the capability to detect and report the reason for
rejecting a submitted program.
Perhaps, gfortran is enforcing the "reject all programs that use
forbidden extensions," portion.
Improvements to the gfortran documentation are encouraged and
welcomed from all users of gfortran that find it lacking.
next prev parent reply other threads:[~2021-08-31 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 14:59 [Bug fortran/102145] New: " ripero84 at gmail dot com
2021-08-31 17:24 ` kargl at gcc dot gnu.org [this message]
2021-09-08 14:14 ` [Bug fortran/102145] " ripero84 at gmail dot com
2021-09-08 16:51 ` sgk at troutmask dot apl.washington.edu
2021-09-12 19:08 ` rimvydas.jas at gmail dot com
2021-09-12 19:09 ` rimvydas.jas at gmail dot com
2021-09-12 19:22 ` kargl at gcc dot gnu.org
2021-09-12 19:34 ` rimvydas.jas at gmail dot com
2021-09-12 22:56 ` sgk at troutmask dot apl.washington.edu
2021-09-12 23:40 ` rimvydas.jas at gmail dot com
2021-09-13 2:52 ` sgk at troutmask dot apl.washington.edu
2021-09-13 5:18 ` rimvydas.jas at gmail dot com
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-102145-4-wP3aDnKEQ0@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).