public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [Patch, fortran] PDT bugs PR2 83611 and 83731
Date: Mon, 08 Jan 2018 11:27:00 -0000	[thread overview]
Message-ID: <CAGkQGiLzS+3248wWyvX5iqnRva+YMULjAg4cSYkrp3XAyBObHQ@mail.gmail.com> (raw)

This patch adds:
(i) Default initializers for parameterized arrays;
(ii) Fixes ordinary assignment of PDTs by implementing the same deep
copy mechanism as for derived types with allocatable components; and
(iii) Fixes the len parameter checking, which failed where the dummy
type had an assumed parameter.

I have in fact committed this patch as revision 256335 since it is
safe for anything other than PDTs.

2018-01-08  Paul Thomas  <pault@gcc.gnu.org>

    PR fortran/83611
    * decl.c (gfc_get_pdt_instance): If parameterized arrays have
    an initializer, convert the kind parameters and add to the
    component if the instance.
    * trans-array.c (structure_alloc_comps): Add 'is_pdt_type' and
    use it with case COPY_ALLOC_COMP. Call 'duplicate_allocatable'
    for parameterized arrays. Clean up typos in comments. Convert
    parameterized array initializers and copy into the array.
    * trans-expr.c (gfc_trans_scalar_assign): Do a deep copy for
    parameterized types.
    *trans-stmt.c (trans_associate_var): Deallocate associate vars
    as necessary, when they are PDT function results for example.

    PR fortran/83731
    * trans-array.c (structure_alloc_comps): Only compare len parms
    when they are declared explicitly.

2018-01-08  Paul Thomas  <pault@gcc.gnu.org>

    PR fortran/83611
    * gfortran.dg/pdt_15.f03 : Bump count of 'n.data = 0B' to 8.
    * gfortran.dg/pdt_26.f03 : Bump count of '_malloc' to 9.
    * gfortran.dg/pdt_27.f03 : New test.

    PR fortran/83731
    * gfortran.dg/pdt_28.f03 : New test.

Cheers

Paul

                 reply	other threads:[~2018-01-08 11:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGkQGiLzS+3248wWyvX5iqnRva+YMULjAg4cSYkrp3XAyBObHQ@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).