From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Mike Lothian <mike@fireburn.co.uk>,
Nathan Chancellor <natechancellor@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org, "H.J. Lu" <hjl.tools@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2] kbuild: Fail if gold linker is detected
Date: Tue, 16 Jul 2019 19:37:08 -0400 [thread overview]
Message-ID: <20190716233708.GA11824@mit.edu> (raw)
In-Reply-To: <alpine.DEB.2.21.1907170015530.1767@nanos.tec.linutronix.de>
On Wed, Jul 17, 2019 at 12:25:14AM +0200, Thomas Gleixner wrote:
> > It's been my default system linker for years and I've had very few issues
> > with it and it's a big improvement when linking with LTO
>
> I understand, but the fact that you need to turn off config options in
> order to build a kernel and the clear statement that it's not recommended
> makes it truly unsuitable and unmaintainable for us.
Or if you work for a cloud company who is willing to make the gold
linker work for your specific use case and configuration (and ideally,
have gold toolchain experts on staff who will work with you), then it
might be OK, but just for that particular use case. (Just as Android
kernels worked with Clang when Clang was still miscompiling kernel on
different architectures and configurations.) In those cases, you can
just carry a patch to force the gold linker to work.
The point though is the teams that were using alternative,
not-always-reliable toolchains, were big boys and girls, and they
weren't asking the upstream kernel devs for support. And they only
cared about a few specific configurations, and not something that
would work for all or even most configurations and hardware platforms.
- Ted
next prev parent reply other threads:[~2019-07-16 23:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 12:47 kbuild: Fail if gold linker is detected Thomas Gleixner
2019-07-16 12:54 ` Peter Zijlstra
2019-07-16 14:40 ` Ingo Molnar
2019-07-16 15:59 ` Thomas Gleixner
2019-07-16 18:13 ` Ingo Molnar
2019-07-16 18:46 ` Linus Torvalds
2019-07-16 18:52 ` Theodore Y. Ts'o
2019-07-29 17:06 ` Bernd Petrovitsch
2019-07-16 17:06 ` Nathan Chancellor
2019-07-16 18:59 ` Thomas Gleixner
2019-07-16 19:47 ` [PATCH v2] " Thomas Gleixner
2019-07-16 19:59 ` Nathan Chancellor
2019-07-16 21:20 ` Mike Lothian
2019-07-16 22:25 ` Thomas Gleixner
2019-07-16 23:37 ` Theodore Y. Ts'o [this message]
2019-07-17 6:54 ` Masahiro Yamada
2019-07-17 7:57 ` Thomas Gleixner
2019-07-20 9:12 ` Mike Lothian
2019-07-20 9:34 ` Thomas Gleixner
2019-07-20 10:13 ` Mike Lothian
2019-07-20 10:54 ` Thomas Gleixner
2019-07-20 10:59 ` Mike Lothian
2019-07-23 1:30 ` Masahiro Yamada
2019-07-23 6:41 ` Thomas Gleixner
2019-07-23 8:17 ` Thomas Gleixner
2019-07-29 2:27 ` Masahiro Yamada
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=20190716233708.GA11824@mit.edu \
--to=tytso@mit.edu \
--cc=hjl.tools@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@fireburn.co.uk \
--cc=natechancellor@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--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