public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/61126] gfortran does not enable -Wununused-parameter with -Wextra Date: Fri, 09 May 2014 15:25:00 -0000 [thread overview] Message-ID: <bug-61126-4-HEWDtac3Nf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61126-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61126 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Matthias Klose from comment #2) > -Wunused-parameter is enabled by -Wall. No, according to the manual it isn't. I think one reason for confusion is the naming of things in the different languages. Named constants are called in Fortran "PARAMETER" and the thing you pass to a procedure (function, subroutine) are called "(actual) arguments" - those get associated with "dummy arguments"/"formal arguments". In C, you call arguments "parameters". Thus, taking about "parameter" is highly confusing. I think it neither really fits to named constants nor to arguments, but since languages have chosen the term ... From the gfortran man page: "-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." >From gcc-bugs-return-451138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 09 15:34:28 2014 Return-Path: <gcc-bugs-return-451138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24172 invoked by alias); 9 May 2014 15:34:28 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 24125 invoked by uid 48); 9 May 2014 15:34:25 -0000 From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/61126] gfortran does not enable -Wununused-parameter with -Wextra Date: Fri, 09 May 2014 15:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: doko at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-61126-4-3LsORRTsbh@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61126-4@http.gcc.gnu.org/bugzilla/> References: <bug-61126-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-05/txt/msg00830.txt.bz2 Content-length: 272 http://gcc.gnu.org/bugzilla/show_bug.cgi?ida126 --- Comment #5 from Matthias Klose <doko at gcc dot gnu.org> --- "-Wunused-parameter is not included in -Wall but is implied by -Wall -Wextra" would mean that the test case assumes that it it is implied by -Wextra only.
next prev parent reply other threads:[~2014-05-09 15:25 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 [this message] 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 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-HEWDtac3Nf@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).