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/45030] -fwhole-file: Bogus error message with ENTRY and different result types Date: Fri, 23 Jul 2010 11:25:00 -0000 [thread overview] Message-ID: <20100723112445.27859.qmail@sourceware.org> (raw) In-Reply-To: <bug-45030-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2010-07-23 11:24 ------- Created an attachment (id=21293) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21293&action=view) Draft patch Draft patch. I was wondering whether one needs to take care of (a) use names in case of use association - or can one not reach that function in this case? (b) C binding names, i.e. subroutine foo() bind(C, name=bar) ... entry foo2() bind(C, name=bar2) ... end interface subroutine Hello() bind(C,name=bar2) end end interface call Hello() ! << this should use the same backend decl as "ENTRY foo2". (c) Whether this just fixes the error checking or whether the backend_decl is also correct. What do you think, Paul? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030
next prev parent reply other threads:[~2010-07-23 11:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-22 13:23 [Bug fortran/45030] New: " burnus at gcc dot gnu dot org 2010-07-22 13:42 ` [Bug fortran/45030] " burnus at gcc dot gnu dot org 2010-07-23 11:25 ` burnus at gcc dot gnu dot org [this message] 2010-07-23 20:08 ` burnus at gcc dot gnu dot org 2010-07-23 20:09 ` burnus at gcc dot gnu dot org [not found] <bug-45030-4@http.gcc.gnu.org/bugzilla/> 2011-12-15 21:56 ` dominiq at lps dot ens.fr 2011-12-16 7:46 ` burnus 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=20100723112445.27859.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).