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/51268] [Regression] A subroutine can not know anymore its own interface
Date: Tue, 29 Nov 2011 15:24:00 -0000 [thread overview]
Message-ID: <bug-51268-4-1I3dY4SG7D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51268-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51268
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
--- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-29 14:44:05 UTC ---
(In reply to comment #10)
> I would say that although I partially disagree the choices made in the Fortran
> Standards in this context, gfortran is not to blame here. So I think this "bug"
> can be closed.
Well, it (and the other compilers) could still be blamed for not implementing
submodules earlier. (For instance, the authors of "Fortran 95/2003 explained"
assumed that it would get implemented before most of the Fortran 2003 features.
As it turned out, it gets implemented as one of the later Fortran 2008 (!)
features.)
CLOSED bug.
prev parent reply other threads:[~2011-11-29 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:32 [Bug fortran/51268] New: " bardeau at iram dot fr
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 [this message]
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-1I3dY4SG7D@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).