From: Ralf Baechle <ralf@linux-mips.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Andi Kleen <ak@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
John Crispin <blogic@openwrt.org>
Subject: Re: [GIT] kbuild/lto changes for 3.15-rc1
Date: Tue, 15 Apr 2014 11:36:22 +0200 [thread overview]
Message-ID: <20140415093622.GB27556@linux-mips.org> (raw)
In-Reply-To: <20140415010003.GA2765@jtriplet-mobl1>
On Mon, Apr 14, 2014 at 06:00:04PM -0700, Josh Triplett wrote:
> > and it slows down
> > kernel development'.
>
> No, it doesn't slow down development builds; it makes kernel builds
> slower if and only if LTO is turned on, which most kernel developers
> won't need to do. On the other hand, distro and embedded kernels can do
> so for final builds, and developers pushing to minimize the kernel can
LTO inherently is going to slow down development because it does inflate
the testing matrix - a developer really should test an LTO build.
That said, the increased checking of the source code for validity across
compilation units done by the LTO final link is a benefit by itself. With
my MIPS maintainer head on I can say it's required fixes / cleanups of
several thousand lines which have already been merged several kernel
versions ago because they all were beneficial even without LTO. A mere
three small commits preparing arch/mips for LTO support and that don't
make sense without LTO are remaining. So it's not a support/testing
nightmare.
And while the code size reduction is less for MIPS than what others have
reported for their platforms (I'm still investigating) is still is enough
that embedded developers would commit murder for.
Ralf
next prev parent reply other threads:[~2014-04-15 9:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 20:19 [GIT] kbuild/lto changes for 3.15-rc1 Michal Marek
2014-04-07 20:59 ` Andi Kleen
2014-04-08 15:26 ` Linus Torvalds
2014-04-08 20:49 ` josh
2014-04-08 22:44 ` Linus Torvalds
2014-04-09 1:35 ` Andi Kleen
2014-04-09 6:01 ` Ingo Molnar
2014-04-09 8:17 ` Markus Trippelsdorf
2014-04-14 10:32 ` Ingo Molnar
2014-04-14 10:46 ` Markus Trippelsdorf
2014-04-14 10:55 ` Ingo Molnar
2014-04-15 1:00 ` Josh Triplett
2014-04-15 1:52 ` Andi Kleen
2014-04-15 6:00 ` Ingo Molnar
2014-04-15 9:36 ` Ralf Baechle [this message]
2014-04-15 11:19 ` Sam Ravnborg
2014-04-15 11:36 ` Markus Trippelsdorf
2014-04-15 18:19 ` Sam Ravnborg
2014-04-15 18:29 ` Markus Trippelsdorf
2014-04-16 6:49 ` Ingo Molnar
2014-04-09 15:40 ` Andi Kleen
2014-04-08 22:49 ` Andi Kleen
2014-04-09 0:10 ` Jan Hubicka
2014-04-09 1:23 ` Andi Kleen
2014-04-09 0:14 ` Tim Bird
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=20140415093622.GB27556@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ak@linux.intel.com \
--cc=blogic@openwrt.org \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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