From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) by sourceware.org (Postfix) with ESMTPS id BCE143857B8A for ; Sat, 30 Jul 2022 18:40:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BCE143857B8A Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oHrNa-0004lu-4l for fortran@gcc.gnu.org; Sat, 30 Jul 2022 20:40:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: fortran@gcc.gnu.org From: Harald Anlauf 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 Message-ID: <4bf99b98-664c-fd8c-121b-b553c5637f41@gmx.de> References: <8e300265-e24c-59c2-19b0-3d74fc5ed425@orange.fr> <2c940b18-08f2-adeb-6ac3-22e89b72440d@orange.fr> <5504785b-7471-f51e-852a-5ef9b039cc21@orange.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Content-Language: en-US In-Reply-To: X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: fortran@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Fortran mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2022 18:40:04 -0000 Message-ID: <20220730183548.I-zGyuZNm_pbEGj1qrVIYkI47db-QZUdab4z-QepzXE@z> 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