public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR87477 - [meta-bug] [F03] issues concerning the ASSOCIATE statement
Date: Thu, 1 Jun 2023 19:58:34 +0200	[thread overview]
Message-ID: <0cb1c0fd-3800-c0a2-f18f-0771e2e65f65@orange.fr> (raw)
In-Reply-To: <CAGkQGiKQcWUnq72PBYJb5YGT6x=tWnO_MhEFA_R7FmPpHE3jSA@mail.gmail.com>

Le 01/06/2023 à 17:20, Paul Richard Thomas via Fortran a écrit :
> Hi All,
> 
> This started out as the search for a fix to pr109948 and evolved to roll in
> 5 other prs.
> 
> Basically parse_associate was far too clunky and, in anycase, existing
> functions in resolve.cc were well capable of doing the determination of the
> target expression rank. While I was checking the comments, the lightbulb
> flashed with respect to prs 102109/112/190 and the chunk dealing with
> function results of unknown type was born.
> 
> Thanks to the changes in parse.cc, the problem in pr99326 migrated
> upstream to the resolution and the chunklet in resolve.cc was an obvious
> fix.
> 
> I am minded to s/{ dg-do run}/{ dg-do compile } for all six testcases.
Makes sense, the PRs were bogus errors and ICEs, so all compile time issues.

> At
> the testing stage, I wanted to check that the testcases actually did what
> they are supposed to do :-)
> 
> Bootstraps and regtests OK - good for head?
> 
OK.  Thanks for this.

> Paul
> 
> PS I need to do some housekeeping on pr87477 now. Some of the blockers have
> "fixed themselves" and others are awaiting backporting. I think that there
> are only 4 or so left, of which 89645 and 99065 are the most difficult to
> deal with.


  reply	other threads:[~2023-06-01 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 15:20 Paul Richard Thomas
2023-06-01 17:58 ` Mikael Morin [this message]
2023-06-02  7:46   ` Paul Richard Thomas
  -- strict thread matches above, loose matches on Subject: below --
2023-03-28 21:04 Paul Richard Thomas
2023-03-29  8:24 ` Manfred Schwarb
2023-03-29  8:53   ` Paul Richard Thomas
2023-04-07  7:02     ` Paul Richard Thomas
2023-04-07  9:40       ` Harald Anlauf

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=0cb1c0fd-3800-c0a2-f18f-0771e2e65f65@orange.fr \
    --to=morin-mikael@orange.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).