From: "Martin Liška" <mliska@suse.cz>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Mailing List <gcc@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] Try LTO partial linking. (Was: Speed of compiling gimple-match.c)
Date: Mon, 24 May 2021 10:07:05 +0200 [thread overview]
Message-ID: <cac13e64-22a5-2895-1e3c-0d3b76eb3742@suse.cz> (raw)
In-Reply-To: <CAGWvny=97e5LQeVOMSPnkPD8sq6C9q2v4a-EeKxaZOF4maDTWw@mail.gmail.com>
On 5/21/21 2:35 PM, David Edelsohn wrote:
> Please remember that not all targets support LTO so a fallback to a
> non-partial-LTO build needs to be provided and automatically invoked
> for those targets.
Sure, for now it's definitely going to be a opt-in, enabled by something like:
make PARTIAL_LTO=1.
Thanks,
Martin
next prev parent reply other threads:[~2021-05-24 8:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+=Sn1=+tuqG7qu5C6_atWzJp+af1P6oVPvABHxqNxiUmJb1dg@mail.gmail.com>
[not found] ` <CAFiYyc1DC1W==r37RhVX9epv1F5XSQhr1XeZEKCk1QOBObSKaQ@mail.gmail.com>
[not found] ` <20210511145904.GM10366@gate.crashing.org>
[not found] ` <CAFiYyc12G6qAeCevEH0-oE4kX7KN1gafBHN4UNYnQJWQVujffg@mail.gmail.com>
[not found] ` <20210512121248.GU10366@gate.crashing.org>
2021-05-20 12:34 ` Martin Liška
2021-05-20 12:54 ` Richard Biener
2021-05-20 13:06 ` Martin Liška
2021-05-20 13:16 ` Richard Biener
2021-05-20 13:22 ` Richard Biener
2021-05-20 15:55 ` Jan Hubicka
2021-05-21 8:29 ` Martin Liška
2021-06-01 7:31 ` Martin Liška
2021-06-23 13:53 ` Martin Liška
2021-08-16 13:58 ` Martin Liška
2021-08-20 14:54 ` Martin Liška
2021-08-22 13:09 ` Jan Hubicka
2021-06-12 15:55 ` Giuliano Belinassi
2021-05-21 8:43 ` Martin Liška
2021-05-21 12:35 ` David Edelsohn
2021-05-24 8:07 ` Martin Liška [this message]
2021-06-01 7:33 ` Martin Liška
2021-06-01 7:42 ` Richard Biener
2021-06-01 11:25 ` Martin Liška
2021-06-01 13:19 ` Richard Biener
2021-08-20 14:57 ` 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=cac13e64-22a5-2895-1e3c-0d3b76eb3742@suse.cz \
--to=mliska@suse.cz \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=segher@kernel.crashing.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).