public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54997] -Wunused-function gives false warnings for procedures passed as actual argument
Date: Sat, 20 Oct 2012 18:45:00 -0000 [thread overview]
Message-ID: <bug-54997-4-fSDYtE2uBf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54997-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54997
--- Comment #3 from janus at gcc dot gnu.org 2012-10-20 18:45:05 UTC ---
(In reply to comment #2)
> Also an "Unused dummy argument" warning is missing here ...
This is fixed by the following patch:
Index: gcc/fortran/decl.c
===================================================================
--- gcc/fortran/decl.c (revision 192619)
+++ gcc/fortran/decl.c (working copy)
@@ -4941,8 +4941,6 @@ match_procedure_decl (void)
}
- gfc_set_sym_referenced (sym);
-
if (gfc_match_eos () == MATCH_YES)
return MATCH_YES;
if (gfc_match_char (',') != MATCH_YES)
next prev parent reply other threads:[~2012-10-20 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 8:50 [Bug fortran/54997] New: " janus at gcc dot gnu.org
2012-10-20 8:58 ` [Bug fortran/54997] " janus at gcc dot gnu.org
2012-10-20 9:03 ` janus at gcc dot gnu.org
2012-10-20 18:45 ` janus at gcc dot gnu.org [this message]
2012-10-20 21:46 ` janus at gcc dot gnu.org
2012-10-21 13:48 ` janus at gcc dot gnu.org
2012-10-22 12:58 ` [Bug fortran/54997] [4.8 Regression] -Wunused-function gives false warnings janus at gcc dot gnu.org
2012-11-07 11:36 ` jakub at gcc dot gnu.org
2012-11-07 17:59 ` janus at gcc dot gnu.org
2012-11-26 11:16 ` janus at gcc dot gnu.org
2012-11-26 11:23 ` janus 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-54997-4-fSDYtE2uBf@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).