From: ndesaulniers@google.com
To: yamada.masahiro@socionext.com
Cc: natechancellor@gmail.com, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [PATCH 0/4] Improve kernel LLD support
Date: Thu, 7 Feb 2019 14:04:35 -0800 [thread overview]
Message-ID: <20190207220435.85367-1-ndesaulniers@google.com> (raw)
This patch cleans up a few places in the Makefile to make way for
landing LLD support in the kernel. There are still a few arch specific
fixes that need to get upstreamed, but this core set of patches should
be arch independent.
Some very rough numbers: LLD is improving the overall build time of
Google Pixel kernels by about 9%. The build is mostly dominated by
compilation, but LLD is able to shave off quite a bit of time.
One of the included patches helps get LLD linked kernels to competitive
binary size, but there still some bugs in LLD causing it not to discard
certain sections. Once that's fixed, I estimate an LLD linked kernel to
be just barely smaller than a BFD linked kernel (less than 1%).
Folks looking to test should use LLD built from source, as I recently
fixed a bug in LLD that prevented LLD linked kernel modules from being
loadable.
$ make LD=ld.lld
Nick Desaulniers (4):
init/Kconfig: add config support for detecting linker
Makefile: clang: choose GCC_TOOLCHAIN_DIR not on LD
Makefile: lld: tell clang to use lld
Makefile: lld: set -O2 linker flag when linking with LLD
Makefile | 9 ++++++++-
init/Kconfig | 9 +++++++++
2 files changed, 17 insertions(+), 1 deletion(-)
--
2.20.1.791.gb4d0f1c61a-goog
reply other threads:[~2019-02-07 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190207220435.85367-1-ndesaulniers@google.com \
--to=ndesaulniers@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®