All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Alistair Strachan <astrachan@google.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: LLD patches for x86_64
Date: Wed, 10 Apr 2019 20:51:43 -0700	[thread overview]
Message-ID: <20190411035143.GA14196@archlinux-i9> (raw)

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

Hi Greg and Sasha,

Please apply the following mbox files to their respective trees. They
contain upstream patches that allow a tip of tree LLD to link an x86
kernel image as well as a patch to avoid using $(LD) to check for
the location of binutils, which won't always be accurate when linking
with LLD. This was tested with both the upstream defconfig and Android's
x86_64_cuttlefish_defconfig in their respective trees (building/linking
with both Clang/LLD and GCC/ld.bfd then booting in QEMU).

For 5.0, a simple cherry-pick of commit ad15006cc784 ("kbuild: clang:
choose GCC_TOOLCHAIN_DIR not on LD") will do.

Greg, the merge into kernel/common will result in two conflicts:

* Makefile:
    Make the diff match upstream commit
        ad15006cc784 ("kbuild: clang: choose GCC_TOOLCHAIN_DIR not on LD")

* arch/x86/entry/vdso/Makefile:
    Take the right hand side, effectively replacing common commit
        35b779802c2e ("x86: vdso: Fix leaky vdso linker with CC=clang.")
    with the proper upstream commit
        379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")

Also, while you are at it, would you mind picking up upstream commit
5f074f3e192f ("lib/string.c: implement a basic bcmp")? It is cc'd for
stable but it's worth mentioning now so we can stop carrying it out of
tree :)

Let me know if there are any issues, comments, or concerns,
Nathan

[-- Attachment #2: lld-4.4.mbox --]
[-- Type: application/mbox, Size: 12465 bytes --]

[-- Attachment #3: lld-4.9.mbox --]
[-- Type: application/mbox, Size: 8713 bytes --]

[-- Attachment #4: lld-4.14.mbox --]
[-- Type: application/mbox, Size: 8839 bytes --]

[-- Attachment #5: lld-4.19.mbox --]
[-- Type: application/mbox, Size: 4214 bytes --]

             reply	other threads:[~2019-04-11  3:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  3:51 Nathan Chancellor [this message]
2019-04-11 13:58 ` LLD patches for x86_64 Sasha Levin
2019-04-11 14:21   ` Nathan Chancellor
2019-04-11 14:25   ` Nathan Chancellor
2019-04-11 14:39     ` Sasha Levin
2019-04-17 18:24 ` Greg Kroah-Hartman
2019-04-17 18:37   ` Nathan Chancellor

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=20190411035143.GA14196@archlinux-i9 \
    --to=natechancellor@gmail.com \
    --cc=astrachan@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ndesaulniers@google.com \
    --cc=samitolvanen@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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.