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/42769] [OOP] ICE in resolve_typebound_procedure Date: Fri, 11 Jun 2010 21:33:00 -0000 [thread overview] Message-ID: <20100611213320.22266.qmail@sourceware.org> (raw) In-Reply-To: <bug-42769-9410@http.gcc.gnu.org/bugzilla/> ------- Comment #24 from janus at gcc dot gnu dot org 2010-06-11 21:33 ------- Here is a somewhat modified version of comment #14, which compiles but produces wrong code: module mod1 type :: t1 contains procedure, nopass :: get => my_get end type contains subroutine my_get() print *,"my_get (mod1)" end subroutine end module module mod2 contains subroutine my_get() ! must have the same name as the function in mod1 print *,"my_get (mod2)" end subroutine end module use mod2 use mod1 ! order of use statements is important type(t1) :: a call a%get() end Output is "my_get (mod2)" while it should be "my_get (mod1)". -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42769
next prev parent reply other threads:[~2010-06-11 21:33 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-16 17:00 [Bug fortran/42769] New: " sfilippone at uniroma2 dot it 2010-01-16 17:02 ` [Bug fortran/42769] " sfilippone at uniroma2 dot it 2010-01-16 17:05 ` sfilippone at uniroma2 dot it 2010-01-16 17:22 ` hjl dot tools at gmail dot com 2010-01-16 17:39 ` dominiq at lps dot ens dot fr 2010-01-16 21:04 ` hjl dot tools at gmail dot com 2010-01-16 21:46 ` [Bug fortran/42769] [4.5 Regression] " burnus at gcc dot gnu dot org 2010-01-17 8:30 ` sfilippone at uniroma2 dot it 2010-01-17 11:59 ` janus at gcc dot gnu dot org 2010-01-17 20:53 ` janus at gcc dot gnu dot org 2010-01-17 21:19 ` hjl dot tools at gmail dot com 2010-01-17 21:21 ` hjl dot tools at gmail dot com 2010-01-17 21:29 ` janus at gcc dot gnu dot org 2010-01-17 21:32 ` dominiq at lps dot ens dot fr 2010-01-17 21:34 ` janus at gcc dot gnu dot org 2010-01-17 21:58 ` [Bug fortran/42769] " janus at gcc dot gnu dot org 2010-01-22 13:20 ` sfilippone at uniroma2 dot it 2010-03-08 14:57 ` dominiq at lps dot ens dot fr 2010-03-08 15:43 ` janus at gcc dot gnu dot org 2010-03-08 15:49 ` dominiq at lps dot ens dot fr 2010-03-08 15:50 ` janus at gcc dot gnu dot org 2010-04-06 11:26 ` rguenth at gcc dot gnu dot org 2010-05-13 20:44 ` dfranke at gcc dot gnu dot org 2010-05-14 11:53 ` [Bug fortran/42769] [OOP] " janus at gcc dot gnu dot org 2010-06-11 21:33 ` janus at gcc dot gnu dot org [this message] 2010-06-11 22:16 ` janus at gcc dot gnu dot org 2010-08-13 17:29 ` janus at gcc dot gnu dot org 2010-08-23 13:26 ` janus at gcc dot gnu dot org 2010-08-23 13:33 ` janus at gcc dot gnu dot org 2010-08-29 21:30 ` janus at gcc dot gnu dot org 2010-08-29 21:36 ` janus at gcc dot gnu dot org [not found] <bug-42769-4@http.gcc.gnu.org/bugzilla/> 2011-02-23 23:36 ` mikael at gcc dot gnu.org 2011-02-24 22:07 ` mikael at gcc dot gnu.org 2011-02-25 0:55 ` mikael at gcc dot gnu.org 2011-03-01 16:27 ` mikael at gcc dot gnu.org 2011-03-25 20:08 ` jakub at gcc dot gnu.org 2011-04-28 16:51 ` rguenth at gcc dot gnu.org 2013-01-06 15:50 ` mikael at gcc dot gnu.org 2013-01-08 19:43 ` mikael at gcc dot gnu.org 2013-01-08 20:02 ` mikael at gcc dot gnu.org 2013-01-09 14:29 ` mikael 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=20100611213320.22266.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).