From: Andre Vehreschild <vehre@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Dominique Dhumieres <dominiq@lps.ens.fr>
Subject: Re: [Fortran, Patch, PR{43366, 57117, 61337, 61376}, v1] Assign to polymorphic objects.
Date: Sat, 22 Oct 2016 13:44:00 -0000 [thread overview]
Message-ID: <20161022143622.170316bb@vepi2> (raw)
In-Reply-To: <CAGkQGiJHTx7UN6VFHgzJm16_TYuZg77jwFQOQKY0VBeHtozPzA@mail.gmail.com>
Hi Paul,
thanks for the review. Committed as r241439.
The first nit has gone to the patch for pr78053 as agreed upon.
The second nit:
> + class(r), allocatable :: foo ! Need this declared of copy_R is not
> generated.
has magically disappeared. I assume that it was necessary on an intermediate
stage of the patch only. I now have stripped the above line from the commit and
everything works fine.
Thanks again for the review.
Regards,
Andre
On Sat, 22 Oct 2016 12:41:19 +0200
Paul Richard Thomas <paul.richard.thomas@gmail.com> wrote:
> Dear Andre,
>
> For the bulk of the patch, I have no comments. However, for the
> testcase alloc_comp_class_5.f03, please eliminate the commented out
> lines and the TODO, as discussed on #gfortran. Add them to the
> testcase for for PR78053, as we agreed.
>
> In realloc_on_assign_27.f08, you have the following lines:
> + class(t), allocatable :: x
> + class(r), allocatable :: foo ! Need this declared of copy_R is not
> generated.
> + type(r) :: y = r (3, 42)
> +
> + x = y
>
> Surely, if you test for the existence of the vtable and create it if
> necessary for the rhs type in gfc_trans_class_assign, that would
> remove the need for 'foo'?
>
> The patch applies cleanly and regtests OK. Apart from the above nits,
> OK for trunk.
>
> Best regards
>
> Paul
>
> On 22 October 2016 at 12:19, Andre Vehreschild <vehre@gmx.de> wrote:
> > Hi Paul,
> >
> > here is the patch for pr78053 so far. It is based on the one for pr43366.
> > Compilation of the also attached testcase now works. Unfortunately produces
> > the patch a lot of regressions because the length of a char array is not
> > stored any longer in the vtab *and* in the _len component for deferred
> > length char arrays. That still has to be fixed. Given that you have
> > modified a lot on how SELECT TYPE works I fear, that when I change there,
> > too, we get a lot of conflicts. So when you have a version of your patch
> > for pr69834 I am happy to review it and continue work on pr78053
> > afterwards. I think this makes the most sense to avoid duplicate or
> > colliding work.
> >
> > Regards,
> > Andre
> >
--
Andre Vehreschild * Email: vehre ad gmx dot de
next prev parent reply other threads:[~2016-10-22 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 12:22 Paul Richard Thomas
2016-10-22 13:44 ` Andre Vehreschild [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-30 20:06 David Edelsohn
2016-11-30 20:51 ` Dominique d'Humières
2016-12-01 18:32 ` Andre Vehreschild
2016-12-01 18:56 ` David Edelsohn
2016-10-13 15:16 Andre Vehreschild
2016-10-19 18:02 ` Andre Vehreschild
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=20161022143622.170316bb@vepi2 \
--to=vehre@gmx.de \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).