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/55352] Erroneous gfortran warning of unused module variable when variable is only used in namelist
Date: Fri, 16 Nov 2012 21:43:00 -0000	[thread overview]
Message-ID: <bug-55352-4-yRMFX6lpno@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55352-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55352

--- Comment #3 from janus at gcc dot gnu.org 2012-11-16 21:43:34 UTC ---
(In reply to comment #2)
> I guess we should either set attr.referenced in gfc_match_namelist (match.c),
> or check for attr.in_namelist in generate_local_decl (trans-decl.c).

The latter is what we do for related cases. Proposed patch:

Index: gcc/fortran/trans-decl.c
===================================================================
--- gcc/fortran/trans-decl.c    (revision 193567)
+++ gcc/fortran/trans-decl.c    (working copy)
@@ -4589,23 +4589,26 @@ generate_local_decl (gfc_symbol * sym)
     }

       /* Warn for unused variables, but not if they're inside a common
-     block, a namelist, or are use-associated.  */
+     block or a namelist.  */
       else if (warn_unused_variable
-           && !(sym->attr.in_common || sym->attr.use_assoc || sym->mark
-            || sym->attr.in_namelist))
+           && !(sym->attr.in_common || sym->mark || sym->attr.in_namelist))
     {
-      gfc_warning ("Unused variable '%s' declared at %L", sym->name,
-               &sym->declared_at);
-      if (sym->backend_decl != NULL_TREE)
-        TREE_NO_WARNING(sym->backend_decl) = 1;
+      if (sym->attr.use_only)
+        {
+          gfc_warning ("Unused module variable '%s' which has been "
+               "explicitly imported at %L", sym->name,
+               &sym->declared_at);
+          if (sym->backend_decl != NULL_TREE)
+        TREE_NO_WARNING(sym->backend_decl) = 1;
+        }
+      else if (!sym->attr.use_assoc)
+        {
+          gfc_warning ("Unused variable '%s' declared at %L",
+               sym->name, &sym->declared_at);
+          if (sym->backend_decl != NULL_TREE)
+        TREE_NO_WARNING(sym->backend_decl) = 1;
+        }
     }
-      else if (warn_unused_variable && sym->attr.use_only)
-    {
-      gfc_warning ("Unused module variable '%s' which has been explicitly "
-               "imported at %L", sym->name, &sym->declared_at);
-      if (sym->backend_decl != NULL_TREE)
-        TREE_NO_WARNING(sym->backend_decl) = 1;
-    }

       /* For variable length CHARACTER parameters, the PARM_DECL already
      references the length variable, so force gfc_get_symbol_decl


  parent reply	other threads:[~2012-11-16 21:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 13:42 [Bug fortran/55352] New: " AstroFloyd at gmail dot com
2012-11-16 13:43 ` [Bug fortran/55352] " AstroFloyd at gmail dot com
2012-11-16 16:31 ` janus at gcc dot gnu.org
2012-11-16 21:43 ` janus at gcc dot gnu.org [this message]
2012-11-17 10:55 ` janus at gcc dot gnu.org
2012-11-18 17:53 ` AstroFloyd at gmail dot com
2012-11-18 19:16 ` janus at gcc dot gnu.org
2012-11-19  9:25 ` [Bug fortran/55352] [4.7/4.8 Regression] " janus at gcc dot gnu.org
2012-11-21 22:20 ` janus at gcc dot gnu.org
2012-11-23 19:05 ` janus at gcc dot gnu.org
2012-11-23 19:10 ` 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-55352-4-yRMFX6lpno@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).