public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37445] Host-associated proc not found if same-name generic is use-associated
Date: Wed, 10 Sep 2008 11:34:00 -0000 [thread overview]
Message-ID: <20080910113305.6230.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37445-15125@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from burnus at gcc dot gnu dot org 2008-09-10 11:33 -------
> actually, I rather sure that gfortran gets it wrong. This would be a
> wrong-code
Unless it were accepts-invalid. (Which I don't think, see below.)
Unfortunately, I yesterday somehow completely missed the second CONTAINS, which
makes putALine an internal procedure to subroutine S3, which changes the
picture as this is no longer a USE-associated issue but a internal procedure
vs. host-associated.
Sorry for misreading this. I believe it is allowed per "16.4.1.3 Host
association", but I cannot find the case of an internal procedure. Maybe it is
also hidden in "16.2 Scope of local identifiers", which rules out some cases
which do not apply (and one could argue it thus allows this not ruled out
case).
In any case, I believe (now that I saw the second CONTAINS) that the programs
in comment 3 and comment 7 are valid.
Sorry again for my misreading.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37445
next prev parent reply other threads:[~2008-09-10 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 15:57 [Bug fortran/37445] New: incorrect error reported clerman at fuse dot net
2008-09-09 16:04 ` [Bug fortran/37445] " clerman at fuse dot net
2008-09-09 18:08 ` jv244 at cam dot ac dot uk
2008-09-09 18:46 ` [Bug fortran/37445] Host-associated proc not found if same-name generic is use-associated burnus at gcc dot gnu dot org
2008-09-09 19:19 ` burnus at gcc dot gnu dot org
2008-09-10 6:39 ` jv244 at cam dot ac dot uk
2008-09-10 6:49 ` jv244 at cam dot ac dot uk
2008-09-10 11:34 ` burnus at gcc dot gnu dot org [this message]
2008-09-10 12:27 ` pault at gcc dot gnu dot org
2008-09-10 12:34 ` pault at gcc dot gnu dot org
2008-09-28 20:40 ` pault at gcc dot gnu dot org
2008-09-29 10:26 ` burnus at gcc dot gnu dot org
2008-09-29 21:40 ` burnus at gcc dot gnu dot org
2008-09-29 22:07 ` burnus at gcc dot gnu dot org
2008-09-30 10:30 ` pault at gcc dot gnu dot org
2008-11-03 6:47 ` pault at gcc dot gnu dot org
2008-11-08 6:22 ` pault at gcc dot gnu dot org
2008-11-08 6:50 ` pault at gcc dot gnu dot 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=20080910113305.6230.qmail@sourceware.org \
--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).