From: Jerry DeLisle <jvdelisle2@gmail.com>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: mscfd@gmx.net
Subject: Re: Ping: [Patch, fortran] PR97694 - ICE with optional assumed rank class(*) argument (and PR97723)
Date: Sun, 27 Dec 2020 18:13:41 -0800 [thread overview]
Message-ID: <aaba9e86-53c5-1c07-0ff9-0860b9a79ecf@gmail.com> (raw)
In-Reply-To: <CAGkQGiK9xAHapXTboYD6FnyADLp_t3pif_9z8SOyC5X4mb2iOw@mail.gmail.com>
LGTM Paul, go for it.
On 12/26/20 8:37 AM, Paul Richard Thomas via Fortran wrote:
> Ping!
>
> On Sat, 12 Dec 2020 at 10:38, Paul Richard Thomas <
> paul.richard.thomas@gmail.com> wrote:
>
>> Fortran: Fix some select rank issues [PR97694 and 97723].
>>
>> Hi All,
>>
>> Unlike select type, select rank selectors retain the allocatable
>> attribute. This is corrected by the chunk in check.c. Note the trailing
>> whitespace corrections. Resolution of select rank construct must be done in
>> the same way as select type and so the break has been added to ensure that
>> the block is resolved in resolve_select_rank. The final chunk prevents
>> segfaults for class associate variables that are optional dummies, since
>> these apparently are not adorned with the GFC_DECL_SAVED_DESCRIPTOR.
>>
>> Regtests OK on FC31/x86_64 - OK for master?
>>
>> Cheers
>>
>> Paul
>>
>> 2020-12-12 Paul Thomas <pault@gcc.gnu.org>
>>
>> gcc/fortran
>> PR fortran/97694
>> PR fortran/97723
>> * check.c (allocatable_check): Select rank temporaries are
>> permitted even though they are treated as associate variables.
>> * resolve.c (gfc_resolve_code): Break on select rank as well as
>> select type so that the block os resolved.
>> * trans-stmt.c (trans_associate_var): Class associate variables
>> that are optional dummies must use the backend_decl.
>>
>> gcc/testsuite/
>> PR fortran/97694
>> PR fortran/97723
>> * gfortran.dg/select_rank_5.f90: New test.
>>
>>
prev parent reply other threads:[~2020-12-28 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 10:38 Paul Richard Thomas
2020-12-26 16:37 ` Ping: " Paul Richard Thomas
2020-12-26 19:01 ` Thomas Koenig
2020-12-27 15:02 ` Paul Richard Thomas
2020-12-28 2:13 ` Jerry DeLisle [this message]
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=aaba9e86-53c5-1c07-0ff9-0860b9a79ecf@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mscfd@gmx.net \
--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).