From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id 243CF3858C54 for ; Wed, 8 Mar 2023 09:10:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 243CF3858C54 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=suse.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.de Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id D00F11FE35; Wed, 8 Mar 2023 09:10:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1678266618; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8foKaBvEidFzoIrHduV9fY6bXAaFX82Xy46Ln0pzyiM=; b=p18cqGBCeav8iWasxHWzP9WD9sEVleoqB0IrmpQi7gaq+4Z6PvNHyv55GJEoQPL0+d2RkK 80bB/UGUtA9G4EQUgJ8MXwJw1NqGi1KAfhk1U2u3TAmJQnaAiqCKj39nq0ktOaFRBGneWf tpbO8RHaPz0PWZ8EqhPb1nI62iOIzYo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1678266618; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8foKaBvEidFzoIrHduV9fY6bXAaFX82Xy46Ln0pzyiM=; b=7/qAaCuM/gorB9MZLAOWugAILgWXe0ej4m/9B93UyalX8bVmuVd3s97l6apItUJO8uJydY i4rL3Ft3wwGjUxDw== Received: from wotan.suse.de (wotan.suse.de [10.160.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 5823D2C141; Wed, 8 Mar 2023 09:10:18 +0000 (UTC) Date: Wed, 8 Mar 2023 09:10:18 +0000 (UTC) From: Richard Biener To: Thomas Koenig cc: Paul Richard Thomas , Steve Kargl , "fortran@gcc.gnu.org" Subject: Re: [Patch, fortran] PR37336 finalization In-Reply-To: Message-ID: References: <582085ac-0d07-a516-732d-e82e0a4e01c9@netcologne.de> User-Agent: Alpine 2.22 (LSU 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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 Wed, 8 Mar 2023, Thomas Koenig wrote: > 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... :/ But at least you can watch https://lnt.opensuse.org after-the-fact > 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. I'd say it probably doesn't use it. But I was more worrying about unwanted side-effects on code _not_ using finalization. Do you know of any medium to large size Fortran code base that uses finalization? Richard.