From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <morin-mikael@orange.fr>
Received: from smtp.smtpout.orange.fr (smtp04.smtpout.orange.fr
 [80.12.242.126])
 by sourceware.org (Postfix) with ESMTPS id 895433856260
 for <fortran@gcc.gnu.org>; Tue, 10 May 2022 11:54:40 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 895433856260
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=orange.fr
Authentication-Results: sourceware.org; spf=none smtp.mailfrom=orange.fr
Received: from [192.168.1.17] ([86.253.179.215]) by smtp.orange.fr with ESMTPA
 id oORlnh3S0ZLw1oORqnq6sk; Tue, 10 May 2022 13:54:38 +0200
X-ME-Helo: [192.168.1.17]
X-ME-Auth: MDU4MTIxYWM4YWI0ZGE4ZTUwZWZmNTExZmI2ZWZlMThkM2ZhYiE5OWRkOGM=
X-ME-Date: Tue, 10 May 2022 13:54:38 +0200
X-ME-IP: 86.253.179.215
Message-ID: <9bcc02bb-df9d-7c6f-14e5-b6a3225298e6@orange.fr>
Date: Tue, 10 May 2022 13:54:33 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.1
Subject: Re: [PATCH] PR fortran/105501 - check for non-optional spaces between
 adjacent keywords
Content-Language: en-US
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
 gcc-patches <gcc-patches@gcc.gnu.org>
References: <trinity-927b057e-4950-4ce5-bf8f-4ec039fab04b-1652041031263@3c-app-gmx-bs41>
 <c874ff05-b698-fa09-bc18-82a31e99603c@orange.fr>
 <37207063-62ba-27b4-8c10-f530c2cd1273@gmx.de>
From: Mikael Morin <morin-mikael@orange.fr>
In-Reply-To: <37207063-62ba-27b4-8c10-f530c2cd1273@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, FREEMAIL_FROM,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_SHORT, NICE_REPLY_A,
 RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: fortran@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Fortran mailing list <fortran.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/fortran>,
 <mailto:fortran-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/fortran/>
List-Help: <mailto:fortran-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/fortran>,
 <mailto:fortran-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2022 11:54:42 -0000

Le 09/05/2022 à 21:34, Harald Anlauf a écrit :
> Hi Mikael,
> 
> Am 09.05.22 um 20:24 schrieb Mikael Morin:
>> The fix itself looks good.  Regarding the test, I don’t understand the
>> problem.  Can’t there be multiple subroutines, each having one (or more)
>> problematic statement(s)?
> 
> that's why I tried but failed.  Example:
> 
> subroutine a
>    errorstop
> end
> subroutine b
>    errorstop
> end
> 
> This now gives just one (the first) error, after which it bails out:
> 
Indeed, I think it’s a bug.
I have submitted a PR for it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105547

Thanks for the patch.