public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Subject: Re: [PATCH, v2] Fortran: fix invalid rank error in ASSOCIATED when rank is remapped [PR77652]
Date: Sat, 30 Jul 2022 20:35:48 +0200	[thread overview]
Message-ID: <4bf99b98-664c-fd8c-121b-b553c5637f41@gmx.de> (raw)
Message-ID: <20220730183548.I-zGyuZNm_pbEGj1qrVIYkI47db-QZUdab4z-QepzXE@z> (raw)
In-Reply-To: <f2bce896-b3ef-b4c6-3267-ba870912849a@orange.fr>

Hi Mikael,

Am 30.07.22 um 12:03 schrieb Mikael Morin:
> Le 28/07/2022 à 22:19, Mikael Morin a écrit :
>> I propose to prepare something tomorrow.
>>
> 
> Here you go.  I haven’t found a procedure, a template or guidelines on 
> wg5-fortran.org, so I’m just asking questions as free text.
> I have not put every combination of cases to limit the number of 
> examples, but an answer for each example should give a good picture.
> Anything to correct or change?  Anything to add?
> 
> Mikael

that pretty much covers all cases and looks good to me.

Thanks for taking this!

Harald


  parent reply	other threads:[~2022-07-30 18:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 20:12 [PATCH] " Harald Anlauf
2022-07-25 10:43 ` Mikael Morin
2022-07-25 16:01   ` Harald Anlauf
2022-07-25 18:08     ` Mikael Morin
2022-07-25 20:18       ` Harald Anlauf
2022-07-26 19:25         ` Mikael Morin
2022-07-27 19:45           ` [PATCH, v2] " Harald Anlauf
2022-07-27 19:45             ` Harald Anlauf
2022-07-27 19:50             ` Toon Moene
2022-07-28 20:19             ` Mikael Morin
2022-07-29 20:01               ` Harald Anlauf
2022-07-29 20:01                 ` Harald Anlauf
2022-07-30 10:03               ` Mikael Morin
2022-07-30 14:13                 ` Toon Moene
2022-07-30 18:35                 ` Harald Anlauf [this message]
2022-07-30 18:35                   ` Harald Anlauf
2022-08-04 12:03                 ` Mikael Morin
2022-08-18 19:32                   ` Harald Anlauf
2022-08-18 19:32                     ` 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=4bf99b98-664c-fd8c-121b-b553c5637f41@gmx.de \
    --to=anlauf@gmx.de \
    --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).