From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"Bader, Reinhold" <Reinhold.Bader@lrz.de>,
Damian Rouson <damian@sourceryinstitute.org>
Subject: [Bug fortran/82173] [meta-bug] Parameterized derived type errors
Date: Sun, 17 Sep 2017 18:29:00 -0000 [thread overview]
Message-ID: <CAGkQGi+3Cg8_8=Z6NChsGj-RBALhY_D1jQqT3FRMeyZ_fQyXzA@mail.gmail.com> (raw)
Dear All,
Reinhold Bader has been feeding me with PDT bugs, most of which are
now fixed in this commit:
Sending gcc/fortran/ChangeLog
Sending gcc/fortran/decl.c
Sending gcc/fortran/primary.c
Sending gcc/fortran/resolve.c
Sending gcc/testsuite/ChangeLog
Adding gcc/testsuite/gfortran.dg/associate_25.f90
Sending gcc/testsuite/gfortran.dg/associate_9.f03
Sending gcc/testsuite/gfortran.dg/pdt_1.f03
Adding gcc/testsuite/gfortran.dg/pdt_11.f03
Adding gcc/testsuite/gfortran.dg/pdt_12.f03
Sending gcc/testsuite/gfortran.dg/pdt_2.f03
Sending gcc/testsuite/gfortran.dg/pdt_3.f03
Sending gcc/testsuite/gfortran.dg/pdt_4.f03
Transmitting file data .............done
Committing transaction...
Committed revision 252894.
Please note that it fixes a rather major problem in ASSOCIATE. I will
go through the PRs and see if others are now fixed.
Cheers
Paul
2017-09-17 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82173
* decl.c (gfc_get_pdt_instance): Use the component initializer
expression for the default, rather than the parameter value.
* resolve.c (resolve_pdt): New function.
(resolve_symbol): Call it. Remove false error, prohibiting
deferred type parameters for dummy arguments.
PR fortran/60483
* primary.c (gfc_match_varspec): If the type of an associate
name is unknown and yet there is a match, try resolving the
target expression and using its type.
2017-09-17 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82173
* gfortran.dg/pdt_1.f03 : Eliminate spurious error checks.
* gfortran.dg/pdt_2.f03 : The same.
* gfortran.dg/pdt_3.f03 : The same.
* gfortran.dg/pdt_4.f03 : Add 'modtype' and two new errors in
module 'bad_vars'. Add error concerning assumed parameters and
save attribute.
* gfortran.dg/pdt_11.f03 : New test.
PR fortran/60483
* gfortran.dg/associate_9.f90 : Remove XFAIL and change to run.
* gfortran.dg/associate_25.f90 : New test.
* gfortran.dg/pdt_12.f03 : New test.
reply other threads:[~2017-09-17 18:29 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='CAGkQGi+3Cg8_8=Z6NChsGj-RBALhY_D1jQqT3FRMeyZ_fQyXzA@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=Reinhold.Bader@lrz.de \
--cc=damian@sourceryinstitute.org \
--cc=fortran@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).