[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210223204919.549167-1-alobakin@pm.me>
Date: Tue, 23 Feb 2021 20:49:42 +0000
From: Alexander Lobakin <alobakin@...me>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Alexander Lobakin <alobakin@...me>,
Kees Cook <keescook@...omium.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sami Tolvanen <samitolvanen@...gle.com>,
Bill Wendling <morbo@...gle.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
George Burgess IV <gbiv@...gle.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Steven Rostedt <rostedt@...dmis.org>,
Will Deacon <will@...nel.org>
Subject: Re: [GIT PULL v2] clang-lto for v5.12-rc1
From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Tue, 23 Feb 2021 12:33:05 -0800
> On Tue, Feb 23, 2021 at 9:49 AM Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > On Mon, Feb 22, 2021 at 3:11 PM Kees Cook <keescook@...omium.org> wrote:
> > >
> > > While x86 LTO enablement is done[1], it depends on some objtool
> > > clean-ups[2], though it appears those actually have been in linux-next
> > > (via tip/objtool/core), so it's possible that if that tree lands [..]
> >
> > That tree is actually next on my list of things to merge after this
> > one, so it should be out soonish.
>
> "soonish" turned out to be later than I thought, because my "build
> changes" set of pulls included the module change that I then wasted a
> lot of time on trying to figure out why it slowed down my build so
> much.
I guess it's about CONFIG_TRIM_UNUSED_KSYMS you disabled in your tree.
Well, it's actually widely used, mostly in the embedded world where
there are often no out-of-tree modules, but a need to save as much
space as possible.
For full-blown systems and distributions it's almost needless, right.
> But it's out now, as pr-tracker-bot already noted.
>
> Linus
Thanks,
Al
Powered by blists - more mailing lists