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/53175] [4.8 Regression] link failure for private module variables used in function specification Date: Fri, 04 May 2012 18:54:00 -0000 [thread overview] Message-ID: <bug-53175-4-OTNkrGWnzB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53175-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53175 --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-05-04 18:54:33 UTC --- Author: burnus Date: Fri May 4 18:54:25 2012 New Revision: 187175 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=187175 Log: 2012-05-04 Tobias Burnus <burnus@net-b.de> PR fortran/53175 * resolve.c (resolve_variable): Set public_used if a private module variable is used in a (public) specification expression. * trans-decl.c (gfc_finish_var_decl): Mark those TREE_PUBLIC. 2012-05-04 Tobias Burnus <burnus@net-b.de> PR fortran/53175 gfortran.dg/public_private_module_5.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/public_private_module_5.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c trunk/gcc/fortran/trans-decl.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-05-04 18:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-01 17:39 [Bug fortran/53175] New: Fortran 4.8 undefined reference to a variable in a module michael.a.richmond at nasa dot gov 2012-05-02 6:00 ` [Bug fortran/53175] [4.8 Regression] link failure for private module variables used in function specification burnus at gcc dot gnu.org 2012-05-02 17:16 ` burnus at gcc dot gnu.org 2012-05-04 18:54 ` burnus at gcc dot gnu.org [this message] 2012-05-04 19:28 ` burnus 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-53175-4-OTNkrGWnzB@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).