From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <morin-mikael@orange.fr>
Received: from smtp.smtpout.orange.fr (smtp-14.smtpout.orange.fr [80.12.242.14])
	by sourceware.org (Postfix) with ESMTPS id 5505938582B0
	for <fortran@gcc.gnu.org>; Sat, 12 Nov 2022 17:39:05 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5505938582B0
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=orange.fr
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=orange.fr
Received: from [192.168.1.17] ([83.197.245.49])
	by smtp.orange.fr with ESMTPA
	id tuT3o2IlYtFxAtuT9ot3Ge; Sat, 12 Nov 2022 18:39:04 +0100
X-ME-Helo: [192.168.1.17]
X-ME-Auth: bW9yaW4tbWlrYWVsQG9yYW5nZS5mcg==
X-ME-Date: Sat, 12 Nov 2022 18:39:04 +0100
X-ME-IP: 83.197.245.49
Message-ID: <5e0c6d2c-9501-da5a-0734-810167866ff6@orange.fr>
Date: Sat, 12 Nov 2022 18:38:57 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.1
Subject: Re: [PATCH] Fortran: fix treatment of character, value, optional
 dummy arguments [PR107444]
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
 gcc-patches <gcc-patches@gcc.gnu.org>
References: <trinity-c4cc511a-5cda-481e-b712-133f9bc73ffe-1668117408459@3c-app-gmx-bs59>
Content-Language: fr
From: Mikael Morin <morin-mikael@orange.fr>
In-Reply-To: <trinity-c4cc511a-5cda-481e-b712-133f9bc73ffe-1668117408459@3c-app-gmx-bs59>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,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
List-Id: <fortran.gcc.gnu.org>

Hello,

Le 10/11/2022 à 22:56, Harald Anlauf via Fortran a écrit :
> Dear Fortranners,
> 
> the attached patch is a follow-up to the fix for PR107441,
> as it finally fixes the treatment of character dummy arguments
> that have the value,optional attribute, and allows for checking
> of the presence of such arguments.
> 
> This entails a small ABI clarification, as the previous text
> was not really clear on the argument passing conventions,
> and the previously generated code was inconsistent at best,
> or rather wrong, for this kind of procedure arguments.
> (E.g. the number of passed arguments was varying...)
> 
> Testcase cross-checked with NAG 7.1.
> 
> Regtested on x86_64-pc-linux-gnu.  OK for mainline?
> 
Looks good.  Thanks.