From: Andrew Stubbs <ams@codesourcery.com>
To: Toon Moene <toon@moene.org>, Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
gcc mailing list <gcc@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: Test with an lto-build of libgfortran.
Date: Fri, 29 Sep 2023 11:26:05 +0100 [thread overview]
Message-ID: <b63b2145-568b-4b26-882c-130715005292@codesourcery.com> (raw)
In-Reply-To: <682f49c9-03d1-45fb-ba4b-ebd3cc92cb1a@moene.org>
On 28/09/2023 20:59, Toon Moene wrote:
> 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.
This sort of thing should definitely Just Work for cross compilers and
embedded platforms where the libraries are bundled with the compiler.
Andrew
next prev parent reply other threads:[~2023-09-29 10:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 Toon Moene
2023-09-27 21:48 ` Jeff Law
2023-09-28 6:25 ` Richard Biener
2023-09-28 6:29 ` Andrew Pinski
2023-09-28 7:29 ` Tobias Burnus
2023-09-28 9:51 ` Jakub Jelinek
2023-09-28 11:00 ` Tobias Burnus
2023-09-28 11:02 ` Jakub Jelinek
2023-09-28 5:33 ` Thomas Koenig
2023-09-28 19:03 ` Toon Moene
2023-09-28 19:26 ` Jakub Jelinek
2023-09-28 19:59 ` Toon Moene
2023-09-28 20:02 ` David Edelsohn
2023-09-29 10:26 ` Andrew Stubbs [this message]
2023-09-29 6:03 ` Thomas Koenig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b63b2145-568b-4b26-882c-130715005292@codesourcery.com \
--to=ams@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tkoenig@netcologne.de \
--cc=toon@moene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).