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/43256] [OOP] TBP with missing optional arg
Date: Fri, 05 Mar 2010 09:36:00 -0000	[thread overview]
Message-ID: <20100305093603.24169.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43256-16146@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from janus at gcc dot gnu dot org  2010-03-05 09:36 -------
(In reply to comment #5)
> All of these throw error messages like
> 
> ABSTRACT INTERFACE '...' must not be referenced at (1)

This was PR41873 and was fixed by querying "expr->value.function.name", which
fails now. We should find a better way to silence this error message for
polymorphic calls.


> Type mismatch in argument '...' at (1); passed CLASS(...) to CLASS(...)

This one is a bit more tricky, but understandable. It is not a problem of the
one-line patch shown above, but of the implementation of polymorphic calls:
When doing a polymorphic call with 'dynamic type /= declared type' of the
passed object and an overridden TBP, we have to convert the passed object to a
CLASS of the dynamic type.


-- 


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


  parent reply	other threads:[~2010-03-05  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 15:44 [Bug fortran/43256] New: [OOP] character-valued " janus at gcc dot gnu dot org
2010-03-04 16:04 ` [Bug fortran/43256] " janus at gcc dot gnu dot org
2010-03-04 16:12 ` [Bug fortran/43256] [OOP] " janus at gcc dot gnu dot org
2010-03-04 21:14 ` janus at gcc dot gnu dot org
2010-03-04 22:11 ` janus at gcc dot gnu dot org
2010-03-04 22:44 ` janus at gcc dot gnu dot org
2010-03-05  9:36 ` janus at gcc dot gnu dot org [this message]
2010-03-05  9:56 ` janus at gcc dot gnu dot org
2010-03-07 14:07 ` janus at gcc dot gnu dot org
2010-03-07 15:59 ` dominiq at lps dot ens dot fr
2010-03-08  9:35 ` janus at gcc dot gnu dot org
2010-03-08  9:37 ` janus 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=20100305093603.24169.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).