linux-kernel - Re: [GIT] kbuild/lto changes for 3.15-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Apr 2014 11:36:22 +0200
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Andi Kleen <ak@...ux.intel.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Marek <mmarek@...e.cz>,
	Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Sam Ravnborg <sam@...nborg.org>,
	John Crispin <blogic@...nwrt.org>
Subject: Re: [GIT] kbuild/lto changes for 3.15-rc1

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/