public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30922] IMPORT fails for same symbol in multiple interface bodies of same interface block Date: Mon, 12 Mar 2007 15:25:00 -0000 [thread overview] Message-ID: <20070312152449.25679.qmail@sourceware.org> (raw) In-Reply-To: <bug-30922-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from pault at gcc dot gnu dot org 2007-03-12 15:24 ------- The testcase in comment 1 should be lifted and deposited in another PR; it is going to be quite difficult to fix because the type and kind of an interface function is established before the specification statements that inlude the IMPORT statement. This problem is related to that of implicit type definition within interfaces that I just fixed (PR30883). Paul -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |pault at gcc dot gnu dot org |dot org | Status|NEW |ASSIGNED Last reconfirmed|2007-03-02 16:14:27 |2007-03-12 15:24:48 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30922
next prev parent reply other threads:[~2007-03-12 15:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-22 9:10 [Bug fortran/30922] New: " burnus at gcc dot gnu dot org 2007-03-02 16:14 ` [Bug fortran/30922] " burnus at gcc dot gnu dot org 2007-03-02 16:16 ` burnus at gcc dot gnu dot org 2007-03-12 8:51 ` burnus at gcc dot gnu dot org 2007-03-12 14:51 ` patchapp at dberlin dot org 2007-03-12 15:25 ` pault at gcc dot gnu dot org [this message] 2007-03-14 4:37 ` brooks at gcc dot gnu dot org 2007-03-14 4:39 ` brooks at gcc dot gnu dot org 2007-03-14 4:48 ` brooks at gcc dot gnu dot org 2007-03-15 6:45 ` pault at gcc dot gnu dot org 2007-03-15 6:55 ` burnus 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=20070312152449.25679.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).