From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CE92CC7618F for ; Tue, 16 Jul 2019 23:37:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ACF4F20651 for ; Tue, 16 Jul 2019 23:37:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389015AbfGPXha (ORCPT ); Tue, 16 Jul 2019 19:37:30 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:39465 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2387623AbfGPXha (ORCPT ); Tue, 16 Jul 2019 19:37:30 -0400 Received: from callcc.thunk.org (guestnat-104-133-0-99.corp.google.com [104.133.0.99] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x6GNb898019260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 16 Jul 2019 19:37:09 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id A0775420054; Tue, 16 Jul 2019 19:37:08 -0400 (EDT) Date: Tue, 16 Jul 2019 19:37:08 -0400 From: "Theodore Y. Ts'o" To: Thomas Gleixner Cc: Mike Lothian , Nathan Chancellor , LKML , Linus Torvalds , x86@kernel.org, "H.J. Lu" , Masahiro Yamada , linux-kbuild@vger.kernel.org Subject: Re: [PATCH v2] kbuild: Fail if gold linker is detected Message-ID: <20190716233708.GA11824@mit.edu> Mail-Followup-To: "Theodore Y. Ts'o" , Thomas Gleixner , Mike Lothian , Nathan Chancellor , LKML , Linus Torvalds , x86@kernel.org, "H.J. Lu" , Masahiro Yamada , linux-kbuild@vger.kernel.org References: <20190716170606.GA38406@archlinux-threadripper> <20190716195957.GA38495@archlinux-threadripper> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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