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/43945] [OOP] Derived type with GENERIC: resolved to the wrong specific TBP Date: Sat, 01 May 2010 17:17:00 -0000 [thread overview] Message-ID: <20100501171657.22753.qmail@sourceware.org> (raw) In-Reply-To: <bug-43945-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from pault at gcc dot gnu dot org 2010-05-01 17:16 ------- I do not see any reason not to confirm this one. This Index: gcc/fortran/resolve.c =================================================================== *** gcc/fortran/resolve.c (revision 158958) --- gcc/fortran/resolve.c (working copy) *************** resolve_typebound_generic_call (gfc_expr *** 5132,5137 **** --- 5132,5138 ---- { gfc_typebound_proc* genproc; const char* genname; + gfc_symtree *st; gcc_assert (e->expr_type == EXPR_COMPCALL); genname = e->value.compcall.name; *************** resolve_typebound_generic_call (gfc_expr *** 5199,5204 **** --- 5200,5214 ---- return FAILURE; success: + genname = e->value.compcall.tbp->u.specific->name; + if (*genname == '@') + genname = e->value.compcall.tbp->u.specific->n.sym->name; + + st = gfc_find_typebound_proc (e->symtree->n.sym->ts.u.derived, NULL, + genname, false, &e->where); + if (st) + e->value.compcall.tbp = st->n.tb; + return SUCCESS; } is a fix for the first testcase - the only regression is dynamic_dispatch_5.f03, which needs dealing with in the same way as the fix for its PR; ie. the derived type needs to be that of the final reference. I'll have something ready by the end of the weekend. 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|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-05-01 17:16:57 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43945
next prev parent reply other threads:[~2010-05-01 17:17 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-30 9:25 [Bug fortran/43945] New: " burnus at gcc dot gnu dot org 2010-04-30 9:25 ` [Bug fortran/43945] " sfilippone at uniroma2 dot it 2010-04-30 9:36 ` burnus at gcc dot gnu dot org 2010-04-30 9:42 ` sfilippone at uniroma2 dot it 2010-04-30 9:43 ` sfilippone at uniroma2 dot it 2010-04-30 9:43 ` sfilippone at uniroma2 dot it 2010-04-30 14:33 ` pault at gcc dot gnu dot org 2010-05-01 17:17 ` pault at gcc dot gnu dot org [this message] 2010-05-05 21:05 ` pault at gcc dot gnu dot org 2010-06-06 2:04 ` janus at gcc dot gnu dot org 2010-06-06 2:29 ` janus at gcc dot gnu dot org 2010-06-06 2:49 ` janus at gcc dot gnu dot org 2010-06-06 3:03 ` janus at gcc dot gnu dot org 2010-06-06 16:21 ` janus at gcc dot gnu dot org 2010-06-07 8:26 ` sfilippone at uniroma2 dot it 2010-06-07 8:27 ` sfilippone at uniroma2 dot it 2010-06-07 9:41 ` burnus at gcc dot gnu dot org 2010-06-08 14:09 ` sfilippone at uniroma2 dot it 2010-06-16 10:32 ` sfilippone at uniroma2 dot it 2010-06-16 10:32 ` sfilippone at uniroma2 dot it 2010-06-21 11:01 ` janus at gcc dot gnu dot org 2010-06-23 12:20 ` sfilippone at uniroma2 dot it 2010-06-25 15:32 ` sfilippone at uniroma2 dot it 2010-06-25 15:35 ` sfilippone at uniroma2 dot it 2010-07-06 10:14 ` sfilippone at uniroma2 dot it 2010-07-06 10:15 ` sfilippone at uniroma2 dot it 2010-07-07 13:15 ` sfilippone at uniroma2 dot it 2010-07-07 14:25 ` sfilippone at uniroma2 dot it 2010-07-11 9:40 ` janus at gcc dot gnu dot org 2010-07-13 8:54 ` burnus at gcc dot gnu dot org 2010-07-13 9:07 ` sfilippone at uniroma2 dot it 2010-07-13 9:12 ` 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=20100501171657.22753.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).