From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cc-smtpout2.netcologne.de (cc-smtpout2.netcologne.de [IPv6:2001:4dd0:100:1062:25:2:0:2]) by sourceware.org (Postfix) with ESMTPS id DD8243857400 for ; Wed, 8 Mar 2023 08:55:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DD8243857400 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=netcologne.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=netcologne.de Received: from cc-smtpin2.netcologne.de (cc-smtpin2.netcologne.de [89.1.8.202]) by cc-smtpout2.netcologne.de (Postfix) with ESMTP id 9AC281257E; Wed, 8 Mar 2023 09:55:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1678265740; bh=TgQfHaGTPYdVET0l5EMIJA+h3LEhmQ/SpblhYH98XkE=; h=Message-ID:Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Waa0CiFJbjotZ8csJIThEFNuG3bDX/IASjPxhqlpZVWttw+oJzhXSkmrhcJgtg3Vk FytcMsvxAg1oZ3q2n0jAgFpyB+6h1zlSrvaPrch95jMX6ToI8GOE1bnKCd6i1PfAd+ iKcFCSG73tyVNVDajiszIbVhaSxkxJ0D0H+iEhQqnMZp/2IGvkYyF8AGldkS6MGVMk AtrODLROS9FZ/WJxoNKfekQboinIEqe71uEjmimQo2PfqMFHieggPUm8LOzgt6Q5dj 1feEH5rVhXlIqI7vzo0LDnn0vVp89zqO9jIqlZaFhtjuyaN7iob/UUeSYkR2wz3C2v rJ0T02sgTmYAQ== Received: from [IPV6:2001:4dd7:c7b6:0:7285:c2ff:fe6c:992d] (2001-4dd7-c7b6-0-7285-c2ff-fe6c-992d.ipv6dyn.netcologne.de [IPv6:2001:4dd7:c7b6:0:7285:c2ff:fe6c:992d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin2.netcologne.de (Postfix) with ESMTPSA id BEEB4120D5; Wed, 8 Mar 2023 09:55:36 +0100 (CET) Message-ID: Date: Wed, 8 Mar 2023 09:55:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [Patch, fortran] PR37336 finalization Content-Language: en-US To: Richard Biener Cc: Paul Richard Thomas , Steve Kargl , "fortran@gcc.gnu.org" References: <582085ac-0d07-a516-732d-e82e0a4e01c9@netcologne.de> From: Thomas Koenig In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-NetCologne-Spam: L X-Rspamd-Action: no action X-Rspamd-Queue-Id: BEEB4120D5 X-Spamd-Bar: / X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 08.03.23 09:14, Richard Biener wrote: > While Fortran is not considered release critical it would be bad to > break say the build of SPEC CPU 2017 or Polyhedron very late in the > cycle. I'd lean towards postponing this to early stage1 and eventually > backport it for GCC 13.2 if you would like this feature to be implemented > for GCC 13. And now comes the problem - no Fortran maintanier has access to SPEC 2017, as far as I know. The curse of closed-source benchmarks... How extensive is SPEC using finalization? My personal guess would be that it is not used extensively, since gfortran's implementation is pretty broken at the moment. Polyhedron we can test, of course, but a grep of the sources shows that finalization is not used there at all. > But it's of course the Fortran maintainers decision. > > Even though Fortran isn't release critical we might ask you to revert > if any such severe problems show up. Sure. Best regards Thomas