From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moene.org (84-86-97-173.fixed.kpn.net [84.86.97.173]) by sourceware.org (Postfix) with ESMTPS id 0D93C385771E; Thu, 28 Sep 2023 20:00:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0D93C385771E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=moene.org Authentication-Results: sourceware.org; spf=none smtp.mailfrom=moene.org Received: from localhost ([127.0.0.1]) by moene.org with esmtp (Exim 4.96) (envelope-from ) id 1qlxB0-0077F2-1P; Thu, 28 Sep 2023 21:59:57 +0200 Message-ID: <682f49c9-03d1-45fb-ba4b-ebd3cc92cb1a@moene.org> Date: Thu, 28 Sep 2023 21:59:57 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Test with an lto-build of libgfortran. Content-Language: en-US To: Jakub Jelinek Cc: Thomas Koenig , gcc mailing list , gfortran References: <9e347fa4-1940-46c6-a5c9-899cf5a7ae85@moene.org> <672da73c-e5d2-4512-8ae9-1c36f14f2b97@moene.org> From: Toon Moene Organization: Moene Computational Physics, Maartensdijk, The Netherlands In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,KHOP_HELO_FCRDNS,SPF_HELO_NONE,SPF_NONE,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: On 9/28/23 21:26, Jakub Jelinek wrote: > It is worse than that, usually the LTO format changes e.g. any time any > option or parameter is added on a release branch (several times a year) and > at other times as well. > Though, admittedly GCC is the single package that actually could get away > with LTO in lib*.a libraries, at least in some packagings (if the static > libraries are in gcc specific subdirectories rather than say /usr/lib{,64} > or similar and if the packaging of gcc updates both the compiler and > corresponding static libraries in a lock-step. Because in that case LTO > in there will be always used only by the same snapshot from the release > branch and so should be compatible with the LTO in it. This might be an argument to make it a configure option, e.g. --enable-lto-runtime. Kind regards, -- Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands