public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "AstroFloyd at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55352] New: Erroneous gfortran warning of unused module variable when variable is only used in namelist Date: Fri, 16 Nov 2012 13:42:00 -0000 [thread overview] Message-ID: <bug-55352-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55352 Bug #: 55352 Summary: Erroneous gfortran warning of unused module variable when variable is only used in namelist Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: AstroFloyd@gmail.com Created attachment 28709 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28709 Minimal example source code gfortran-4.7.2 -Wall gives a warning about unused module variables when those variables are only used in a namelist. Test: compile the attached minimal example source file test.f90 with: gfortran -v -Wall -Werror test.f90 -o test The following warning is printed: test.f90:14.6: use data, only: a 1 Warning: Unused module variable 'a' which has been explicitly imported at (1) The warning goes away when print*,a is uncommented in line 20. Verbose output is in the attached file compile_output.txt Get: warning about unused module variable Expect: no warning Reproduceable: always gfortran version: gcc version 4.7.2 (Gentoo 4.7.2 p1.3, pie-0.5.5)
next reply other threads:[~2012-11-16 13:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-16 13:42 AstroFloyd at gmail dot com [this message] 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 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@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).