public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49693] Spurious "unused-variable" warnings for COMMON block module variables.
Date: Sun, 01 Jan 2012 16:37:00 -0000 [thread overview]
Message-ID: <bug-49693-4-oexDQuUBV2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49693-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49693
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2012-01-01 16:37:27 UTC ---
Testing this patch:
Index: toplev.c
===================================================================
--- toplev.c (Revision 182754)
+++ toplev.c (Arbeitskopie)
@@ -501,6 +501,9 @@
to handle multiple external decls in different scopes. */
&& ! (DECL_NAME (decl) && TREE_USED (DECL_NAME (decl)))
&& ! DECL_EXTERNAL (decl)
+ /* Don't warn about variables in Fortran common blocks because
+ they may be used elsewhere. */
+ && ! DECL_COMMON(decl)
&& ! TREE_PUBLIC (decl)
/* A volatile variable might be used in some non-obvious way. */
&& ! TREE_THIS_VOLATILE (decl)
next prev parent reply other threads:[~2012-01-01 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 22:25 [Bug fortran/49693] New: " stephan.kramer at imperial dot ac.uk
2011-08-12 19:39 ` [Bug fortran/49693] " longb at cray dot com
2011-12-30 0:26 ` harald at klimachs dot de
2012-01-01 16:37 ` tkoenig at gcc dot gnu.org [this message]
2012-01-03 12:36 ` tkoenig at gcc dot gnu.org
2012-01-04 11:52 ` tkoenig at gcc dot gnu.org
2012-01-04 11:56 ` tkoenig at gcc dot gnu.org
2012-01-04 18:41 ` harald at klimachs dot de
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-49693-4-oexDQuUBV2@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).