public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute Date: Mon, 26 May 2008 18:44:00 -0000 [thread overview] Message-ID: <20080526184406.1875.qmail@sourceware.org> (raw) In-Reply-To: <bug-36325-14773@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from janus at gcc dot gnu dot org 2008-05-26 18:44 ------- Created an attachment (id=15687) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15687&action=view) patch version 2 The attached new version of the patch fixes the reduction3.f90 testcase by deleting the interface statement (the "intrinsic" has to stay I think). Moreover it includes another related bugfix (see PR35830 comment #2). Regarding Tobi's comment #7: interface real function bar() end function bar end interface dimension :: bar(4) Why would I need to reject this? At least it's compatible with conflict(external with implicit interface, dimension) because it has an explicit interface. I think the problem is rather that the dimension statement contradicts the interface statement, which says that 'bar' returns a scalar real number (and not an array). g95's error message is: dimension :: bar(4) 1 Error: Attribute declaration of 'bar' at (1) is outside of the INTERFACE body So I guess it is indeed invalid (and accepted by gfortran), but this seems to be unrelated to this PR (probably it deserves a separate PR). Apart from this I see no remaining problems. The patch regtests without any failures. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36325
next prev parent reply other threads:[~2008-05-26 18:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-25 13:36 [Bug fortran/36325] New: " jaydub66 at gmail dot com 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 [this message] 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=20080526184406.1875.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: 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).