public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46849] [OOP] MODULE PROCEDURE resolution does not work in BLOCK or SELECT TYPE Date: Wed, 08 Dec 2010 13:48:00 -0000 [thread overview] Message-ID: <bug-46849-4-wwCkR5gB1B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46849-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46849 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2010.12.08 13:48:45 Ever Confirmed|0 |1 --- Comment #3 from janus at gcc dot gnu.org 2010-12-08 13:48:45 UTC --- Here is a reduced test case for the rejects-valid part, without CLASS and ISO_C_BINDING: implicit none block call init(fun) end block contains subroutine init(func) real, external :: func end subroutine real function fun() fun = 1.1 end function end
next prev parent reply other threads:[~2010-12-08 13:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-08 13:07 [Bug fortran/46849] New: " burnus at gcc dot gnu.org 2010-12-08 13:08 ` [Bug fortran/46849] " burnus at gcc dot gnu.org 2010-12-08 13:30 ` burnus at gcc dot gnu.org 2010-12-08 13:48 ` janus at gcc dot gnu.org [this message] 2010-12-13 21:59 ` janus at gcc dot gnu.org 2010-12-14 8:36 ` burnus at gcc dot gnu.org 2010-12-14 12:13 ` janus at gcc dot gnu.org 2010-12-14 18:31 ` janus at gcc dot gnu.org 2010-12-17 12:32 ` janus at gcc dot gnu.org 2010-12-17 12:34 ` janus at gcc dot gnu.org 2011-02-14 10:30 ` janus 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=bug-46849-4-wwCkR5gB1B@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).