From: Paul Bolle <pebolle@tiscali.nl>
To: Andi Kleen <ak@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
gleb@redhat.com, hpa@zytor.com, hubicka@ucw.cz,
linux-kernel@vger.kernel.org, mingo@kernel.org,
pbonzini@redhat.com, perex@perex.cz, peterz@infradead.org,
rostedt@goodmis.org, rusty@rustcorp.com.au, tglx@linutronix.de
Subject: Re: [GIT PULL] x86 LTO changes for v3.15
Date: Wed, 02 Apr 2014 10:29:26 +0200 [thread overview]
Message-ID: <1396427366.18431.23.camel@x220> (raw)
In-Reply-To: <20140401231741.GM32556@tassilo.jf.intel.com>
On Tue, 2014-04-01 at 16:17 -0700, Andi Kleen wrote:
> On Tue, Apr 01, 2014 at 10:49:51PM +0200, Paul Bolle wrote:
> > I can't find a Kconfig symbol LTO nor a preprocessor define for
> > CONFIG_LTO. (I only checked master of Linus's tree and linux-next.)
>
> The patch for LTO is not merged yet, this is all preparation.
>
> >
> > Why is this check for CONFIG_LTO needed?
>
> The comment just below describes the problem.
>
> Or is your question what LTO is? Link Time Optimization
I asked the wrong question, as I wanted to ask whether a Kconfig symbol
LTO is perhaps pending somewhere. You basically answered that question
already.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2014-04-02 8:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 21:05 [GIT PULL] x86 LTO changes for v3.15 H. Peter Anvin
2014-03-31 21:54 ` Linus Torvalds
2014-03-31 23:03 ` Andi Kleen
2014-04-01 0:17 ` Linus Torvalds
2014-04-01 0:33 ` Linus Torvalds
2014-04-01 18:54 ` H. Peter Anvin
2014-04-01 19:15 ` Linus Torvalds
2014-04-01 19:43 ` H. Peter Anvin
2014-04-02 0:01 ` Steven Rostedt
2014-04-02 0:35 ` Linus Torvalds
2014-04-02 12:33 ` Steven Rostedt
2014-04-02 17:10 ` H. Peter Anvin
2014-04-02 17:59 ` Steven Rostedt
2014-04-01 1:09 ` Andi Kleen
2014-04-01 1:35 ` H. Peter Anvin
2014-04-01 2:26 ` Linus Torvalds
2014-04-01 20:49 ` Paul Bolle
2014-04-01 23:17 ` Andi Kleen
2014-04-02 8:29 ` Paul Bolle [this message]
2014-04-16 8:53 ` Viresh Kumar
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=1396427366.18431.23.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=ak@linux.intel.com \
--cc=gleb@redhat.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=hubicka@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.