From: Toon Moene <toon@moene.org>
To: Thomas Koenig <tkoenig@netcologne.de>,
gcc mailing list <gcc@gcc.gnu.org>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: Test with an lto-build of libgfortran.
Date: Thu, 28 Sep 2023 21:03:39 +0200 [thread overview]
Message-ID: <672da73c-e5d2-4512-8ae9-1c36f14f2b97@moene.org> (raw)
In-Reply-To: <a338b60c-5aef-4aa1-2d15-8989b5e49250@netcologne.de>
On 9/28/23 07:33, Thomas Koenig wrote:
> Hi Toon,
[ I wrote: ]
>> The full question of "lto-ing" run time libraries is more complicated
>> than just "whether it works" as those who attended the BoF will recall.
>
> I didn't attend the Cauldron (but that discussion would have been
> very interesting). I think for libgfortran, a first step would be
> additional work to get declarations on both sides to agree (which is
> worth doing anyway).
>
> Best regards
>
> Thomas
The big problem in *distributing* GCC (i.e., the collection) with lto'd
run-time libraries is that the format of the lto structure changes with
releases. If a compiler (by accident) picks up a run time library with
non-matching lto objects, it might crash (or "introduce subtle errors in
a once working program").
I.e., like the problem the gfortran community had with the changing
format of our .mod files.
But it would be a big win for Fortran ...
Kind regards,
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
next prev parent reply other threads:[~2023-09-28 19:03 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 [this message]
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
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=672da73c-e5d2-4512-8ae9-1c36f14f2b97@moene.org \
--to=toon@moene.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).