public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52669] No warning in unused private variable in modules Date: Mon, 15 Jul 2013 06:33:00 -0000 [thread overview] Message-ID: <bug-52669-4-1U1akZUo8m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52669-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52669 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- Author: tkoenig Date: Sun Jul 14 19:16:56 2013 New Revision: 200950 URL: http://gcc.gnu.org/viewcvs?rev=200950&root=gcc&view=rev Log: 2013-07-14 Thomas Koenig <tkoenig@gcc.gnu.org> Tobias Burnus <burnus@gcc.gnu.org> PR fortran/52669 * trans-decl.c (gfc_finish_var_decl): Move setting of PRIVATE for a module variable if the module has a private default or -fmodule-private is given to... (gfc_create_module_variable): here. Optionally warn about private module variable which is not used. 2013-07-14 Thomas Koenig <tkoenig@gcc.gnu.org> PR fortran/52669 * fortran.dg/module_variable_1.f90: New test. * fortran.dg/module_variable_2.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/module_variable_1.f90 trunk/gcc/testsuite/gfortran.dg/module_variable_2.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-decl.c trunk/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2013-07-15 6:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-22 15:45 [Bug fortran/52669] New: " arnaud02 at users dot sourceforge.net 2012-03-22 16:26 ` [Bug fortran/52669] " burnus at gcc dot gnu.org 2013-07-11 22:19 ` tkoenig at gcc dot gnu.org 2013-07-15 6:33 ` burnus at gcc dot gnu.org [this message]
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-52669-4-1U1akZUo8m@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).