From: Thomas Koenig <tkoenig@netcologne.de>
To: "Martin Liška" <mliska@suse.cz>,
"Andrew Pinski" <pinskia@gmail.com>,
"Jan Hubicka" <hubicka@ucw.cz>
Cc: Richard Biener <richard.guenther@gmail.com>,
Jeff Law <law@redhat.com>, GCC Development <gcc@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
fortran@gcc.gnu.org
Subject: Re: [RFC] zstd as a compression algorithm for LTO
Date: Thu, 20 Jun 2019 12:12:00 -0000 [thread overview]
Message-ID: <d32366f3-8b9c-d299-9e33-1743fb1c4f17@netcologne.de> (raw)
In-Reply-To: <9417a329-c71c-4682-872c-60ff3524c47e@suse.cz>
Hi Martin,
> LTO bytecode is not supposed to be a distributable format.
One of my dreams is to make libgfortran LTO-clean. There is
a lot of performance to be gained both in I/O (where a huge
number of special cases could be shortcut by LTO, because
hardly any program uses them all) and in array intrinsics,
where seeing through the array descriptors can also lead
to large benefits. This is PR 77278.
Once this is achieved, it would make sense to distribute
libgfortran.a as a library of fat object files.
Regards
Thomas
next prev parent reply other threads:[~2019-06-20 12:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 9:21 Martin Liška
2019-06-19 16:03 ` Jeff Law
2019-06-19 18:55 ` Richard Biener
2019-06-19 19:26 ` Andrew Pinski
2019-06-19 19:29 ` Jan Hubicka
2019-06-19 19:34 ` Andrew Pinski
2019-06-20 9:08 ` Martin Liška
2019-06-20 10:59 ` Thomas Koenig
2019-06-20 11:42 ` Martin Liška
2019-06-20 12:02 ` Jan Hubicka
2019-06-21 10:20 ` [PATCH] Add .gnu.lto_.meta section Martin Liška
2019-06-21 12:34 ` Richard Biener
2019-06-21 12:49 ` Martin Liška
2019-06-21 12:57 ` Jan Hubicka
2019-06-21 14:01 ` Martin Liška
2019-06-24 12:02 ` Richard Biener
2019-06-24 12:12 ` Martin Liška
2019-06-24 12:44 ` Richard Biener
2019-06-24 13:31 ` Martin Liška
2019-06-24 14:25 ` Iain Sandoe
2019-06-24 18:05 ` Richard Biener
2019-06-25 8:14 ` Martin Liška
2019-06-25 14:15 ` Richard Biener
2019-06-27 12:28 ` [PATCH] Add .gnu.lto_.lto section Martin Liška
2019-07-01 10:59 ` Martin Liška
2019-07-01 11:01 ` [PATCH 2/2] Add zstd support for LTO bytecode compression Martin Liška
2019-07-02 20:50 ` Jeff Law
2019-07-02 20:49 ` [PATCH] Add .gnu.lto_.lto section Jeff Law
2019-06-20 12:12 ` Thomas Koenig [this message]
2019-06-20 17:02 ` [RFC] zstd as a compression algorithm for LTO Joseph Myers
2019-06-20 10:46 ` Segher Boessenkool
2019-06-20 11:44 ` Martin Liška
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=d32366f3-8b9c-d299-9e33-1743fb1c4f17@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=mliska@suse.cz \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.com \
/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).