From: Andi Kleen <ak@linux.intel.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
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>
Subject: Re: [GIT] kbuild/lto changes for 3.15-rc1
Date: Mon, 14 Apr 2014 18:52:33 -0700 [thread overview]
Message-ID: <20140415015233.GE32556@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140415010003.GA2765@jtriplet-mobl1>
> > 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
> turn it on for their own work as needed.
Yes and the patch even takes special care that you will not enable
it by mistake.
-Andi
next prev parent reply other threads:[~2014-04-15 1:52 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 [this message]
2014-04-15 6:00 ` Ingo Molnar
2014-04-15 9:36 ` Ralf Baechle
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=20140415015233.GE32556@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--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