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/41603] [-fwhole-file] Add diagnostic for assumed-length character function
Date: Tue, 06 Oct 2009 15:01:00 -0000 [thread overview]
Message-ID: <20091006150138.19511.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41603-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from burnus at gcc dot gnu dot org 2009-10-06 15:01 -------
(In reply to comment #2)
> If the latter is the correct reading then one needs to have an implicit
> interface with a character length (which is not "*, cf. PR 41604), but using
> an explicit interface is not allowed.
That's also in line with NAG f95. If one replaces the interface block by
external assumed_len
character(4) assumed_len
NAG f95 compiles without error.
("ifort -warn all" still gives the same bogus warning as in comment 0. The
warning for the related but different construct at PR 41604 seems to be correct
and it is only printed by ifort.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41603
next prev parent reply other threads:[~2009-10-06 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 14:26 [Bug fortran/41603] New: " burnus at gcc dot gnu dot org
2009-10-06 14:27 ` [Bug fortran/41603] " burnus at gcc dot gnu dot org
2009-10-06 14:57 ` burnus at gcc dot gnu dot org
2009-10-06 15:01 ` burnus at gcc dot gnu dot org [this message]
2009-10-06 17:56 ` burnus at gcc dot gnu dot org
2009-10-07 8:02 ` burnus at gcc dot gnu dot org
2009-10-14 16:10 ` burnus at gcc dot gnu dot org
[not found] <bug-41603-4@http.gcc.gnu.org/bugzilla/>
2011-03-13 15:54 ` pault 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=20091006150138.19511.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).