public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jaydub66 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36325] New: specific or generic INTERFACE implies the EXTERNAL attribute Date: Sun, 25 May 2008 13:36:00 -0000 [thread overview] Message-ID: <bug-36325-14773@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1684 bytes --] I think the following code is invalid: interface subroutine foo end subroutine end interface external foo Because the INTERFACE statement already specifies the EXTERNAL attribute, which is thus specified twice. This code *is* actually rejected (as of rev. 135859), but the error message is completely wrong: external :: foo 1 Error: EXTERNAL attribute conflicts with SUBROUTINE attribute at (1) (which it does *not* for this case) Quoting the Fortran 2003 standard (section 5.1.2.6): "The EXTERNAL attribute speciï¬es that an entity is an external procedure, dummy procedure, procedure pointer, or block data subprogram. This attribute may also be speciï¬ed by an EXTERNAL statement (12.3.2.2), a procedure-declaration-stmt (12.3.2.3) or an interface body that is not in an abstract interface block (12.3.2.1)." And further on in section 12.3.2.1: "An interface body in a generic or speciï¬c interface block speciï¬es the EXTERNAL attribute and an explicit speciï¬c interface for an external procedure or a dummy procedure. If the name of the declared procedure is that of a dummy argument in the subprogram containing the interface body, the procedure is a dummy procedure; otherwise, it is an external procedure." -- Summary: specific or generic INTERFACE implies the EXTERNAL attribute Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jaydub66 at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36325
next reply other threads:[~2008-05-25 13:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-25 13:36 jaydub66 at gmail dot com [this message] 2008-05-25 14:03 ` [Bug fortran/36325] " jaydub66 at gmail dot com 2008-05-25 14:46 ` jaydub66 at gmail dot com 2008-05-25 15:37 ` burnus at gcc dot gnu dot org 2008-05-25 16:37 ` janus at gcc dot gnu dot org 2008-05-25 17:12 ` burnus at gcc dot gnu dot org 2008-05-25 19:09 ` janus at gcc dot gnu dot org 2008-05-25 19:59 ` burnus at gcc dot gnu dot org 2008-05-25 22:33 ` janus at gcc dot gnu dot org 2008-05-26 16:50 ` burnus at gcc dot gnu dot org 2008-05-26 18:44 ` janus at gcc dot gnu dot org 2008-05-26 20:34 ` burnus at gcc dot gnu dot org 2008-05-28 21:29 ` janus at gcc dot gnu dot org 2008-05-28 21:38 ` janus 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=bug-36325-14773@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: linkBe 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).