public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "longb at cray dot com" <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: Fri, 12 Aug 2011 19:39:00 -0000 [thread overview]
Message-ID: <bug-49693-4-sy5FIjUuER@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
Bill Long <longb at cray dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |longb at cray dot com
--- Comment #1 from Bill Long <longb at cray dot com> 2011-08-12 19:22:50 UTC ---
Had a user support with similar issues when using the MPI module. Test case:
module dmi_mpi_global
use mpi
implicit none
private
logical, save, public :: debug_print
integer(4), save, public :: iu06
integer(4), save, public :: mpi_io_rank = 0
character(LEN=256), save, public :: mpi_decomp_file = 'mpi_decompo.txt'
public :: dmpi_close
contains
subroutine dmpi_close ( flag )
implicit none
logical, intent(in) :: flag
integer(4) :: ierr
if (flag) then
write(*,'(a19)') 'Time to die for MPI'
else
write(iu06,'(a19)') 'Time to die for MPI'
endif
if (.not.flag) close (iu06)
call mpi_finalize(ierr)
end subroutine dmpi_close
end module dmi_mpi_global
> ftn -c -Wall test.f90
test.f90:2:0: warning: 'mpi_bottom' defined but not used [-Wunused-variable]
test.f90:2:0: warning: 'mpi_in_place' defined but not used [-Wunused-variable]
test.f90:2:0: warning: 'mpi_status_ignore' defined but not used
[-Wunused-variable]
test.f90:2:0: warning: 'mpi_statuses_ignore' defined but not used
[-Wunused-variable]
test.f90:2:0: warning: 'mpi_errcodes_ignore' defined but not used
[-Wunused-variable]
test.f90:2:0: warning: 'mpi_unweighted' defined but not used
[-Wunused-variable]
test.f90:2:0: warning: 'mpi_argvs_null' defined but not used
[-Wunused-variable]
test.f90:2:0: warning: 'mpi_argv_null' defined but not used [-Wunused-variable]
next prev parent reply other threads:[~2011-08-12 19:23 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 ` longb at cray dot com [this message]
2011-12-30 0:26 ` [Bug fortran/49693] " harald at klimachs dot de
2012-01-01 16:37 ` tkoenig at gcc dot gnu.org
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-sy5FIjUuER@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).