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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8B0B5C433FE for ; Fri, 8 Apr 2022 16:15:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=cgwAt6SSNFD5in9TR8p+3k2SkLQXeVrJ6/oDjRDA/A8=; b=sRg/2fJuVbtTLU HGP0DMY2kqCrTA5RPKmFPlLAMxsj0khu/8yDs+oHcob8y021ZGwaIv9eCjBPZ3kFHniWe/pJRBFrU GQAaSzsH+oE3tEMdQmf5eVsmpKRnIf2dAajae3eDzfYuZ0CHtRv1xwowi8kc0Rel+IIKC+kN/QbQG khQ2U5304Ooj9YM78HGV3mNssY6+3T20FwKFpQcmLGRzYNJX3DIgOBPpwDECKggxgIhL7METMU/Ko 4GJtmTs8ZE7McmJOVgkTFnfmr7HhqHRDp2LLHIw2YNtMc3SjSlKaA43iacoJk8z3kkV5BrW8H6Zg2 iwonoBuW1Gi+KFPkrjuA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncrFG-000QcU-9r; Fri, 08 Apr 2022 16:13:58 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncrF9-000QYm-2d for linux-arm-kernel@lists.infradead.org; Fri, 08 Apr 2022 16:13:55 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A0CDD62086; Fri, 8 Apr 2022 16:13:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B5FAAC385A1; Fri, 8 Apr 2022 16:13:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649434430; bh=JEz3Ik6Fe1BwhfN49WC3fZK6yA4TQchHahuE2Awf3QY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CeCnuNMXAXqzZigJuNp7BBmUhsexZyLtjJkxK3L/7OTHbcamrAdNZrYD03+GW48fh a46ySBunZL2cpy0Fji8LSqGwwpyYQ44UgNJZxjfUFb4eRVqK6hA/oPZy1Tr+mBsrDd e0ZHk+dZwz+hDyw+D5ZNCAKgvz/HYtdHf3Z95WQEwj04n06XCBNe2pgAsfJLZWGD5w uTJBJvFGyl6ah/+C913bGIEDjZm/YDhKnJl8my+qIxHu/AWaUnoztLgsjt+Uyfrsag 2Ypc69YHF39rJ0OVoxTpE2GKfHwnwaruhALmnWDEY/VV7+mQIzt89m8UUmkO9W4ZNX z2Oo8GYo8aJtw== Date: Fri, 8 Apr 2022 17:13:44 +0100 From: Will Deacon To: Mark Rutland Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com, keescook@chromium.org, ardb@kernel.org, nathan@kernel.org Subject: Re: allmodconfig builds failing to link on arm64 Message-ID: <20220408161344.GA28108@willie-the-truck> References: <20220408115407.GA27685@willie-the-truck> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220408_091351_298769_559165D0 X-CRM114-Status: GOOD ( 25.63 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Apr 08, 2022 at 04:06:39PM +0100, Mark Rutland wrote: > On Fri, Apr 08, 2022 at 03:45:42PM +0100, Mark Rutland wrote: > > On Fri, Apr 08, 2022 at 12:54:07PM +0100, Will Deacon wrote: > > > Since -rc1 (although I haven't tried bisecting the merge window), I'm > > > not able to link allmodconfig for arm64: > > > > > > aarch64-linux-gnu-ld: .init.data has both ordered [`__patchable_function_entries' in init/main.o] and unordered [`.init_array.1' in virt/lib/irqbypass.o] sections > > > aarch64-linux-gnu-ld: final link failed: bad value > > > make: *** [Makefile:1158: vmlinux] Error 1 > > > > > > I'm using an Android clang based on 12.0.6 and LD claims to be > > > 2.33.1.20191209. > > > > I can reproduce that when using the llvm.org 12.0.0 binaries along with the > > kernel.org crosstool 9.2.0 binaries (binutils 2.32) to build v5.18-rc1 > > allmodconfig. > > > > I see the failure with (at least) the following combinations that I tested: > > > > * LLVM 11.0.0 && binutils 2.34 (kernel.org 8.4.0 binaries) > > * LLVM 12.0.0 && binutils 2.30 (kernel.org 8.1.0 binaries) > > * LLVM 12.0.0 && binutils 2.32 (kernel.org 9.2.0 binaries) > > * LLVM 12.0.0 && binutils 2.34 (kernel.org 8.4.0/9.3.0 binaries) > > * LLVM 13.0.0 && binutils 2.34 (kernel.org 8.4.0 binaries) > > * LLVM 14.0.0 && binutils 2.34 (kernel.org 8.4.0 binaries) > > > > I *DO NOT* see the failure with the following combinations: > > > > * LLVM 12.0.0 && binutils 2.36.1 (kernel.org 10.3.0/11.1.0 binaries) > > * LLVM 13.0.0 && binutils 2.36.1 (kernel.org 10.3.0/11.1.0 binaries) > > * LLVM 14.0.0 && binutils 2.36.1 (kernel.org 10.3.0/11.1.0 binaries) > > > > So clearly something changed on the binutils side between 2.34 and > > 2.36.1, but I don't know whether either behaviour is incorrect, or > > whether LLVM implicitly depends upon a newer binutils version. > > > > I don't know why this suddenly became a problem in v5.18-rc1; I'll have > > a look. > > I also see this with earlier kernel versions, including: > > * v5.15 allmodconfig, LLVM 12.0.0, binutils 2.30 (kernel.org 8.1.0 binaries) > * v5.16 allmodconfig, LLVM 12.0.0, binutils 2.30 (kernel.org 8.1.0 binaries) > * v5.17 allmodconfig, LLVM 12.0.0, binutils 2.30 (kernel.org 8.1.0 binaries) > > ... so it doesn't look like this is a (recent) regression. Damn, sorry for the mis-diagnosis then. I only just started seeing it, but thinking about it I _usually_ build with LLVM=1 which probably rules out binutils entirely. For some reason, I ended up in the mixed case today and ran into this. In any case, it would be good to get it resolved and I'm happy to test out any fixes. Cheers, Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel