Stable Archive on
 help / color / Atom feed
From: Sasha Levin <>
To: Nathan Chancellor <>
Cc: Greg Kroah-Hartman <>,, Alistair Strachan <>,
	Sami Tolvanen <>,
	Nick Desaulniers <>
Subject: Re: LLD patches for x86_64
Date: Thu, 11 Apr 2019 09:58:04 -0400
Message-ID: <20190411135804.GI11568@sasha-vm> (raw)
In-Reply-To: <20190411035143.GA14196@archlinux-i9>

On Wed, Apr 10, 2019 at 08:51:43PM -0700, Nathan Chancellor wrote:
>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")


I might be missing something, but ad15006cc784 does not touch
arch/x86/entry/vdso/Makefile nor does it generate any conflicts.


  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  3:51 Nathan Chancellor
2019-04-11 13:58 ` Sasha Levin [this message]
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 publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190411135804.GI11568@sasha-vm \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Stable Archive on

Archives are clonable:
	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone