From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.smtpout.orange.fr (smtp-11.smtpout.orange.fr [80.12.242.11]) by sourceware.org (Postfix) with ESMTPS id E55753858D32 for ; Tue, 26 Jul 2022 07:02:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E55753858D32 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] ([86.215.161.154]) by smtp.orange.fr with ESMTPA id GEa7oCNGgvbzbGEaEoNs33; Tue, 26 Jul 2022 09:02:24 +0200 X-ME-Helo: [192.168.1.17] X-ME-Auth: MDU4MTIxYWM4YWI0ZGE4ZTUwZWZmNTExZmI2ZWZlMThkM2ZhYiE5OWRkOGM= X-ME-Date: Tue, 26 Jul 2022 09:02:24 +0200 X-ME-IP: 86.215.161.154 Message-ID: <6f7a182a-8fb2-151f-2e10-08ea107e2cca@orange.fr> Date: Tue, 26 Jul 2022 09:02:15 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH] Fortran: error recovery from calculation of storage size of a symbol [PR103504] Content-Language: fr To: Harald Anlauf , fortran , gcc-patches References: From: Mikael Morin In-Reply-To: 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, 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: Tue, 26 Jul 2022 07:02:27 -0000 Le 25/07/2022 à 22:39, Harald Anlauf via Fortran a écrit : > Dear all, > > we currently may ICE when array bounds of a dummy argument have > a non-integer type, and the procedure with the bad declaration is > referenced. The same applies to bad character length of dummies. > We could simply punt in such a situation, as the causing error > seems to be reliably diagnosed, see testcase. > > Regtested on x86_64-pc-linux-gnu. OK for mainline? > Yes. > This is a really safe fix and potentially backportable to other > open branches. Would that be fine? > I think it is. Thanks.