public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul dot richard dot thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42385] [OOP] poylmorphic operators do not work
Date: Mon, 19 Jul 2010 20:12:00 -0000 [thread overview]
Message-ID: <20100719201239.5818.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42385-16146@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
------- Comment #9 from paul dot richard dot thomas at gmail dot com 2010-07-19 20:12 -------
Subject: Re: [OOP] poylmorphic operators do not work
Fixed on trunk
Paul
> Author: pault
> Date: Mon Jul 19 18:48:44 2010
> New Revision: 162313
>
> URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162313
> Log:
> 2010-07-19 Paul Thomas <pault@gcc.gnu.org>
>
> PR fortran/42385
> * interface.c (matching_typebound_op): Add argument for the
> return of the generic name for the procedure.
> (build_compcall_for_operator): Add an argument for the generic
> name of an operator procedure and supply it to the expression.
> (gfc_extend_expr, gfc_extend_assign): Use the generic name in
> calls to the above procedures.
> * resolve.c (resolve_typebound_function): Catch procedure
> component calls for CLASS objects, check that the vtable is
> complete and insert the $vptr and procedure components, to make
> the call.
> (resolve_typebound_function): The same.
> * trans-decl.c (gfc_trans_deferred_vars): Do not deallocate
> an allocatable scalar if it is a result.
>
>
> 2010-07-19 Paul Thomas <pault@gcc.gnu.org>
>
> PR fortran/42385
> * gfortran.dg/class_defined_operator_1.f03 : New test.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42385
next prev parent reply other threads:[~2010-07-19 20:12 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
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 [this message]
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=20100719201239.5818.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).