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] [4.7/4.8 Regression] Erroneous gfortran warning of unused module variable when variable is only used in namelist
Date: Fri, 23 Nov 2012 19:05:00 -0000	[thread overview]
Message-ID: <bug-55352-4-6b6xQCmJnP@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 #9 from janus at gcc dot gnu.org 2012-11-23 19:05:20 UTC ---
Author: janus
Date: Fri Nov 23 19:05:14 2012
New Revision: 193766

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193766
Log:
2012-11-23  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/55352
    * trans-decl.c (generate_local_decl): Don't warn for explicitly imported
    but unused module variables which are in a namelist or common block.

2012-11-23  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/55352
    * gfortran.dg/namelist_76.f90: New.

Added:
    branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/namelist_76.f90
Modified:
    branches/gcc-4_7-branch/gcc/fortran/ChangeLog
    branches/gcc-4_7-branch/gcc/fortran/trans-decl.c
    branches/gcc-4_7-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-11-23 19:05 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
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 [this message]
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-6b6xQCmJnP@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).