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/54221] [4.8 Regression] Explicit private access specifier signals "unexpected defined but not used [-Wunused-function]" warning Date: Tue, 21 Aug 2012 08:54:00 -0000 [thread overview] Message-ID: <bug-54221-4-43rz33GcfT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54221-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54221 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 Target Milestone|--- |4.8.0 Summary|Explicit private access |[4.8 Regression] Explicit |specifier signals |private access specifier |"unexpected defined but not |signals "unexpected defined |used [-Wunused-function]" |but not used |warning |[-Wunused-function]" | |warning --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-08-21 08:53:48 UTC --- I mark this now as regression in the Fortran front-end to keep better track of PR middle-end/54224: It seems as if part of the fix has to be done in the Fortran front-end. In this PR, the issue of having a different result with PRIVATE vs. "PRIVATE :: entry_name" is now fixed. It remains the issue that there is no warning for unused internal procedures (or unused nested functions in C), no warning of unused PRIVATE module variables and a spurious warning for *used* PRIVATE module procedures. Those are tracked in PR 54224. Additionally, there is the issue that the private module procedures is not inlined, see other PR and PR 48636 comment 18.
next prev parent reply other threads:[~2012-08-21 8:54 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-10 12:59 [Bug fortran/54221] New: " koen.poppe at cs dot kuleuven.be 2012-08-10 15:36 ` [Bug fortran/54221] " burnus at gcc dot gnu.org 2012-08-11 9:06 ` burnus at gcc dot gnu.org 2012-08-12 9:53 ` burnus at gcc dot gnu.org 2012-08-21 8:54 ` burnus at gcc dot gnu.org [this message] 2012-10-09 19:54 ` [Bug fortran/54221] [4.8 Regression] " janus at gcc dot gnu.org 2013-03-22 14:45 ` [Bug fortran/54221] [4.8/4.9 " jakub at gcc dot gnu.org 2013-05-31 10:59 ` jakub at gcc dot gnu.org 2013-10-16 9:49 ` jakub at gcc dot gnu.org 2013-12-29 12:40 ` dominiq at lps dot ens.fr 2014-01-09 12:28 ` janus at gcc dot gnu.org 2014-01-09 16:56 ` abensonca at gmail dot com 2014-01-10 10:23 ` janus at gcc dot gnu.org 2015-09-13 13:45 ` dominiq at lps dot ens.fr 2015-09-13 13:48 ` dominiq at lps dot ens.fr 2015-09-13 15:24 ` dominiq at lps dot ens.fr
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-54221-4-43rz33GcfT@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).