Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp2850709ybi; Sun, 28 Jul 2019 19:29:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqxRN1MR12yK7CH+n4q3bQ3uZ4JrRA+LzGa2HaaoTONzzmigrYRxjkI8Lp5mda6bfq8XX6Xl X-Received: by 2002:a17:902:e512:: with SMTP id ck18mr102201203plb.53.1564367341747; Sun, 28 Jul 2019 19:29:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564367341; cv=none; d=google.com; s=arc-20160816; b=rJGIYJ/QPnRRBcZsyfpimPA+lE0wDrK/lTKhSrQHrNRnYF37wDay18KQeVuWvYi/Ev HTOF6Yzh8bwxHWfW0JFfgQpaamK/3rS416Xxox3s8SYratECYswzgvtvrnpEeCpmDIXf HZClcP6NzPHTt3bPfvUtdDB7PNymUjjkSWp6t7RfaIY99vCaaTVMo3V8gbpYysqbukcj s06NRyWU6Mk3x2T7aDhWKc7HeE6w/uFtUJ54KDbW0sArjWVYVP7fo+ypGqS3vcy2qj1d DCvGdVmDpio+zJKe2UKozFecBL7+Eglt0roglEb6oKaw53GinxR3QjDiZByHOpI0YQy4 GprQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature:dkim-filter; bh=fuZnDsZpEjCp0F5PNZMcUKY5REV4m18B0lrZlOvAENw=; b=uMOUI3CxbTZg+FTuRfCi1t3ZoQd7uf7kKF3Hvyadvj2DfUfEgCifsv3VnDcjPmjHr6 NVcoQDkYodxBqytwQWheEUMDJZNYJP/qEV1dxcmIEu2E5LNp/1/zqet1wsUvhOti9JBS 4Z0wwssu6hkbJrpyxEET/WuBuSeMqwJDeRSzRDADzOebDZFA9mGLFzJT+nY06XW05UH2 kFyK2Xa5QtW0e88R/Ik1tVyT+DI88/8EQRj2KT8YB1/EhLPpuoFC7Ofv0MaKePQzxLQy 1uSNpiV2GD+g+/6s3vl/jx4GMr+/TQrsM0QmBnEr2NF8G/UhwnTtTw5tPVAxg8uPbYwS pQXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=vsUZVzRX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a190si26830834pgc.25.2019.07.28.19.28.45; Sun, 28 Jul 2019 19:29:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=vsUZVzRX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726417AbfG2C2K (ORCPT + 99 others); Sun, 28 Jul 2019 22:28:10 -0400 Received: from conssluserg-04.nifty.com ([210.131.2.83]:46479 "EHLO conssluserg-04.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726216AbfG2C2K (ORCPT ); Sun, 28 Jul 2019 22:28:10 -0400 Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) (authenticated) by conssluserg-04.nifty.com with ESMTP id x6T2RvWA017712; Mon, 29 Jul 2019 11:27:57 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com x6T2RvWA017712 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1564367278; bh=fuZnDsZpEjCp0F5PNZMcUKY5REV4m18B0lrZlOvAENw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=vsUZVzRXAnGOJXyG6FvMBKTegKUZilyCP9sDOxJzbUlCUMKwl8aWmKG32OqWEHkWx Hy4JlKv7FEfsnoB1xZiypCxZK9Ge38s2v74tDlkAJlIrpR7r7c1NIjZED3n8+4Uw4E ipuRBmaQys67OgDpP7YipMVvktuSxdfIFrtVk/0ornkNux5le1yqbbSRQzyVy6LauS T1sDhvTOi9oeLHwSsSnVxsOozf43oDqV2vb+ej9iWIuvhfb1WF3hDg/5qsAQjwxnXQ 4k504SAAFYq03KSVoBK/vIO9uPi41tCJDixaN8vv2DTkcPEGHqzN2JHgbYKceh3XZL N9pRIBiBAJk6g== X-Nifty-SrcIP: [209.85.217.53] Received: by mail-vs1-f53.google.com with SMTP id a186so38168529vsd.7; Sun, 28 Jul 2019 19:27:57 -0700 (PDT) X-Gm-Message-State: APjAAAVxRRDhVu/ZFnm+xM6+FL9iwvoPVR/iWKN0V/ys5BizT6WZek7A sA15JcPEWwflJkHuRFjcEf//1oaI9SqJQrgkTPY= X-Received: by 2002:a67:d46:: with SMTP id 67mr66750201vsn.181.1564367276406; Sun, 28 Jul 2019 19:27:56 -0700 (PDT) MIME-Version: 1.0 References: <20190716170606.GA38406@archlinux-threadripper> In-Reply-To: From: Masahiro Yamada Date: Mon, 29 Jul 2019 11:27:20 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2] kbuild: Fail if gold linker is detected To: Thomas Gleixner Cc: Mike Lothian , Nathan Chancellor , LKML , Linus Torvalds , X86 ML , "H.J. Lu" , Linux Kbuild mailing list , "Theodore Y. Ts'o" , linux-arch Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 23, 2019 at 5:17 PM Thomas Gleixner wrote: > > On Tue, 23 Jul 2019, Thomas Gleixner wrote: > > On Tue, 23 Jul 2019, Masahiro Yamada wrote: > > > Right. > > > I was able to build with ld.gold > > > > > > So, we can use gold, depending on the kernel configuration. > > > > That's exactly the problem. It breaks with random kernel configurations > > which is not acceptable except for people who know what they are doing. > > > > I'm tired of dealing with half baken fixes and 'regression' reports. Either > > there is an effort to fix the issues with gold like the clang people fix > > their issues or it needs to be disabled. We have a clear statement that > > gold developers have other priorities. > > That said, I'm perfectly happy to move this to x86 and leave it alone for > other architectures, but it does not make sense to me. I did not see opposition from other arch maintainers. > If the gold fans care enough, then we can add something like > CONFIG_I_WANT_TO_USE_GOLD_AND_DEAL_WITH_THE_FALLOUT_MYSELF. Let's apply this and see. If somebody really wants to use gold by his risk, I will consider such a config option. Applied to linux-kbuild. Thanks. -- Best Regards Masahiro Yamada