public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bardeau at iram dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51268] New: [Regression] A subroutine can not know anymore its own interface
Date: Tue, 22 Nov 2011 13:32:00 -0000 [thread overview]
Message-ID: <bug-51268-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51268
Bug #: 51268
Summary: [Regression] A subroutine can not know anymore its own
interface
Classification: Unclassified
Product: gcc
Version: fortran-dev
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: bardeau@iram.fr
Created attachment 25881
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25881
Declare a subroutine interface and use this interface in the subroutine
This a regression which appeared in the last months: problem is in 4.7.0
20111119 but not in 4.7.0 20110507
In the latest version, a subroutine can not know its own interface and an error
is raised about duplicate symbols (see example attached):
test.f90:15.6:
use myinterfaces
1
Error: 'mysub' of module 'myinterfaces', imported at (1), is also the name of
the current program unit
>From our developer point of view, this is a very annoying regression, since we
are in charge of several libraries, with hundreds of subroutines in each. We
made the choice to provide all the interfaces of all the subroutines to all of
them, in order to ensure a correct use of the subroutines everywhere. For each
library we thus have a dedicated interface module which is used everywhere.
Forbidding a subroutine to know its own interface would imply to use the
statement "use only", which is definitely not well suited for large programs.
Thanks for your help.
next reply other threads:[~2011-11-22 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:32 bardeau at iram dot fr [this message]
2011-11-22 16:42 ` [Bug fortran/51268] " burnus at gcc dot gnu.org
2011-11-23 9:34 ` bardeau at iram dot fr
2011-11-23 10:54 ` burnus at gcc dot gnu.org
2011-11-23 14:20 ` bardeau at iram dot fr
2011-11-23 17:17 ` burnus at gcc dot gnu.org
2011-11-24 14:14 ` bardeau at iram dot fr
2011-11-24 14:45 ` burnus at gcc dot gnu.org
2011-11-24 16:35 ` bardeau at iram dot fr
2011-11-29 14:29 ` burnus at gcc dot gnu.org
2011-11-29 14:48 ` bardeau at iram dot fr
2011-11-29 15:24 ` 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-51268-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).