public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61126] [4.10 Regression] gfortran does not enable -Wununused-parameter with -Wextra
Date: Thu, 15 May 2014 10:11:00 -0000 [thread overview]
Message-ID: <bug-61126-4-nBsepTdVll@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61126-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61126
--- Comment #21 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > -Wunused-parameter is enabled by -Wall.
>
> No, according to the manual it isn't.
The gfortran manual reads:
-Wunused-parameter
Contrary to gcc's meaning of -Wunused-parameter, gfortran's implementation of
this option does not warn about unused dummy arguments (see
-Wunused-dummy-argument), but about unused PARAMETER values. -Wunused-parameter
is not included in -Wall but is implied by -Wall -Wextra.
This should probably be changed if -Wunused-parameter is implied by -Wextra.
Note that if -Wextra can be used alone without implying -Wall, it is yet
another poor choice for the -W naming (starting with -Wall which is not all
warnings at all).
next prev parent reply other threads:[~2014-05-15 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 12:38 [Bug fortran/61126] New: " fweimer at redhat dot com
2014-05-09 13:11 ` [Bug fortran/61126] " dominiq at lps dot ens.fr
2014-05-09 15:24 ` fweimer at redhat dot com
2014-05-09 15:25 ` burnus at gcc dot gnu.org
2014-05-09 15:51 ` burnus at gcc dot gnu.org
2014-05-09 16:03 ` manu at gcc dot gnu.org
2014-05-09 16:16 ` manu at gcc dot gnu.org
2014-05-09 16:46 ` manu at gcc dot gnu.org
2014-05-09 22:21 ` manu at gcc dot gnu.org
2014-05-10 11:51 ` doko at ubuntu dot com
2014-05-12 16:18 ` doko at gcc dot gnu.org
2014-05-14 2:03 ` [Bug fortran/61126] [4.8/4.9/4.10 Regression] " hp at gcc dot gnu.org
2014-05-14 2:10 ` hp at gcc dot gnu.org
2014-05-14 16:27 ` [Bug fortran/61126] [4.10 " doko at gcc dot gnu.org
2014-05-15 10:11 ` dominiq at lps dot ens.fr [this message]
2014-05-15 10:44 ` manu at gcc dot gnu.org
2014-05-26 14:03 ` rguenth at gcc dot gnu.org
2014-06-18 6:27 ` burnus 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-61126-4-nBsepTdVll@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).