[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFy8hWqBpF1TXOPvA2rRaZp=H2LTO3wd3AERspmcGZhAeQ@mail.gmail.com>
Date: Tue, 8 Apr 2014 08:26:09 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Michal Marek <mmarek@...e.cz>
Cc: Andi Kleen <ak@...ux.intel.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT] kbuild/lto changes for 3.15-rc1
On Mon, Apr 7, 2014 at 1:19 PM, Michal Marek <mmarek@...e.cz> wrote:
>
> besides the kbuild branch, here is the LTO build support by Andi. It is
> a separate branch, because it depends on other patches by Andi which
> were merged through other trees. The link-time-optimization build is an
> experimental feature, so there one kconfig option to enable it and
> another kconfig option to disable it (behind a door with a sign "Beware
> of the Leopard"...), so that it is not enabled by
> allmodconfig/allyesconfig.
So right now, I see several reasons not to merge it ("It's so
experimental that we don't even want to encourage people to test it"
to "it's not fully fleshed out yet and makes compile times _much_
longer").
And yet nobody has actually talked about why I *should* merge it.
Which - I think understandably - makes me less than enthusiastic.
So I think I'll let this wait a bit longer, _unless_ people start
talking about the upsides. How much smaller is the end result? How
much faster is it? How much more beautiful is it? Does it make new
cool things possible? Are those cool things really close on the
horizon and really want this merged even though it's not really quite
ready yet?
So please: convince me. Andi?
Linus
--
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/
Powered by blists - more mailing lists