From: Segher Boessenkool <segher@kernel.crashing.org>
To: Richard Biener <rguenther@suse.de>
Cc: "Martin Liška" <mliska@suse.cz>,
gcc-patches@gcc.gnu.org,
"Richard Sandiford" <richard.sandiford@arm.com>
Subject: Re: [RFH] split {generic,gimple}-match.c files
Date: Thu, 02 May 2019 17:00:00 -0000 [thread overview]
Message-ID: <20190502170016.GJ8599@gate.crashing.org> (raw)
In-Reply-To: <alpine.LSU.2.20.1905021511590.10704@zhemvz.fhfr.qr>
On Thu, May 02, 2019 at 03:18:00PM +0200, Richard Biener wrote:
> Somewhen earlier this year I've done the experiment with using
> a compile with -flto -fno-fat-lto-objects and a link
> via -flto -r -flinker-output=rel into the object file. This cut
> compile-time more than in half with less maintainance overhead.
>
> Adding other files to this handling looks trivial as well, as well
> as conditionalizing it (I'd probably not want this for devel builds).
But we want devel builds to be a lot faster than they are now :-/
Segher
next prev parent reply other threads:[~2019-05-02 17:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 11:44 Richard Biener
2018-04-25 12:26 ` Richard Biener
2018-04-25 12:46 ` Richard Biener
2018-04-25 13:16 ` Martin Liška
2018-09-03 12:27 ` Martin Liška
2018-09-03 12:41 ` Richard Biener
2018-09-03 12:54 ` Martin Liška
2018-09-03 13:50 ` Martin Liška
2018-09-03 14:01 ` Richard Biener
2018-09-03 14:27 ` Martin Liška
2018-09-03 14:43 ` Richard Biener
2018-09-04 15:07 ` Martin Liška
2018-09-10 11:43 ` Martin Liška
2019-04-29 15:21 ` Martin Liška
2019-05-02 13:18 ` Richard Biener
2019-05-02 17:00 ` Segher Boessenkool [this message]
2019-05-02 17:41 ` Richard Biener
2019-05-02 18:14 ` Segher Boessenkool
2019-05-02 19:04 ` Richard Biener
2019-05-06 12:59 ` Martin Liška
2019-05-06 13:36 ` Richard Biener
2019-05-06 13:51 ` Martin Liška
2019-05-06 15:10 ` Segher Boessenkool
2019-05-06 12:56 ` Martin Liška
2019-05-06 13:32 ` Richard Biener
2019-05-06 13:50 ` Martin Liška
2019-04-29 14:41 ` 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=20190502170016.GJ8599@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.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).