public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sfilippone at uniroma2 dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42385] [OOP] poylmorphic operators do not work
Date: Tue, 13 Jul 2010 09:24:00 -0000	[thread overview]
Message-ID: <20100713092417.29867.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42385-16146@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from sfilippone at uniroma2 dot it  2010-07-13 09:24 -------
(In reply to comment #4)
> Carry on the test case from PR 43945 comment 19 (cf. also PR 43945 comment 30,
> 31, 32):
> 
> 
> As the test case in comment 3 (attachment 21184 [edit]) is different from the one of
> PR 43945 comment 19, I add the latter as well:
> 
> Attachment 20927 [edit]  compiles with both crayftn and gfortran, but the run-time
> result is different; while crayftn has
> 
>  Allocated COO succesfully, should now set components
>  STOP
> 
> with gfortran the result is
> 
>  Error: Missing ovverriding impl for allocate in class COO
> 

The two are intended to generate the same error, i.e. resolution to the base
specific instead of the overriding one. As far as I can tell the error is
caused by having a binding-name => specific-name in the base version; if the
base version has just a name (thus binding==specific) the resolution mechanism
works.

Salvatore 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42385


  parent reply	other threads:[~2010-07-13  9:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 23:01 [Bug fortran/42385] New: " janus at gcc dot gnu dot org
2010-05-21 14:02 ` [Bug fortran/42385] " damian at rouson dot net
2010-07-12 14:59 ` sfilippone at uniroma2 dot it
2010-07-12 14:59 ` sfilippone at uniroma2 dot it
2010-07-13  9:18 ` burnus at gcc dot gnu dot org
2010-07-13  9:24 ` sfilippone at uniroma2 dot it [this message]
2010-07-14 21:43 ` burnus at gcc dot gnu dot org
2010-07-16 13:20 ` pault at gcc dot gnu dot org
2010-07-19 18:49 ` pault at gcc dot gnu dot org
2010-07-19 20:12 ` paul dot richard dot thomas at gmail dot com
2010-07-20  8:09 ` 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=20100713092417.29867.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: link
Be 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).