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/54884] New: [4.8 Regression] Externally used PRIVATE module procedure wrongly marked as TREE_PUBLIC()=0
Date: Wed, 10 Oct 2012 07:30:00 -0000 [thread overview]
Message-ID: <bug-54884-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54884
Bug #: 54884
Summary: [4.8 Regression] Externally used PRIVATE module
procedure wrongly marked as TREE_PUBLIC()=0
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: burnus@gcc.gnu.org
CC: abensonca@gmail.com
As reported by Andrew Benson at
http://gcc.gnu.org/ml/fortran/2012-10/msg00046.html:
Build the FoX library (http://www1.gly.bris.ac.uk/~walker/FoX/), specifically
the version at
http://www1.gly.bris.ac.uk/~walker/FoX/source/FoX-4.1.2-full.tar.gz
leads to link errors:
m_wxml_core.F90:(.text+0x1a2): undefined reference to
`__m_common_attrs_MOD_get_value_by_index_len'
gfortran 4.8 marks PRIVATE module variables/procedures as TREE_PUBLIC()=0,
however, that shouldn't happen if they are externally visible. In that case,
they shall be marked as attr.public_used - which seemingly doesn't happen in
this case.
In ./common/m_common_attrs.F90 one has:
module m_common_attrs
private
!...
public :: get_key
contains
pure function get_key_len(dict, i) result(n)
!...
end function get_key_len
! ...
function get_key(dict, i) result(key)
! ...
character(len=get_key_len(dict,i)) :: key
end function get_key
end module m_common_attrs
next reply other threads:[~2012-10-10 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 7:30 burnus at gcc dot gnu.org [this message]
2012-10-10 7:36 ` [Bug fortran/54884] " dominiq at lps dot ens.fr
2012-10-10 7:42 ` burnus at gcc dot gnu.org
2012-10-10 8:40 ` rguenth at gcc dot gnu.org
2012-10-10 9:08 ` janus at gcc dot gnu.org
2012-10-10 13:24 ` dominiq at lps dot ens.fr
2012-10-18 17:09 ` burnus at gcc dot gnu.org
2012-10-19 10:07 ` burnus at gcc dot gnu.org
2012-12-19 17:32 ` abensonca at gmail dot com
2012-12-19 18:03 ` abensonca at gmail dot com
2012-12-19 18:20 ` burnus at gcc dot gnu.org
2012-12-21 12:13 ` rguenth at gcc dot gnu.org
2012-12-23 18:43 ` burnus at gcc dot gnu.org
2012-12-23 18:45 ` 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-54884-4@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).