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: Wed, 02 May 2012 06:00:00 -0000 [thread overview]
Message-ID: <bug-53175-4-F0PhfVMnGp@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
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Keywords| |rejects-valid
Last reconfirmed| |2012-05-02
CC| |burnus at gcc dot gnu.org
Ever Confirmed|0 |1
Summary|Fortran 4.8 undefined |[4.8 Regression] link
|reference to a variable in |failure for private module
|a module |variables used in function
| |specification
Target Milestone|--- |4.8.0
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-05-02 06:00:08 UTC ---
The regression has been caused by PR 52751 (cf. also PR 40973 and PR 52916).
The patch for those PRs marks the module variable "DIM" as nonpublic, which
increases the optimization possibilities for the compiler. However, "dim" is
used for the type parameter of the result variable of two (public) functions.
The solution is to do the same as for PR 52916 - but this time for module
variables: Setting attr.public_used for the module variable if it is used as
type parameter of public functions - even if those are only available
indirectly via generic interfaces.
next prev parent reply other threads:[~2012-05-02 6:00 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 ` burnus at gcc dot gnu.org [this message]
2012-05-02 17:16 ` [Bug fortran/53175] [4.8 Regression] link failure for private module variables used in function specification burnus at gcc dot gnu.org
2012-05-04 18:54 ` burnus at gcc dot gnu.org
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-F0PhfVMnGp@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).