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 CD421C433EF for ; Fri, 24 Jun 2022 14:12:05 +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=kc0d/DJbS9mku59ilB0HTlmg6KWxY/19uGKxqCLB2WE=; b=bbHSlEXqtCKz8J F9YMAM8v2NRFsxNDWTxaKgBTveMt1GbV2nID0BevOAwuU8KIFHNwJnIgO1l24pNIOvMVaJ7D/QPje gh6fD0bRKMcbm4zlp8syxRI6hsenQZ07/mCzcXjHgsOdp5tBFPOB594CYos7IyT+/cOcSi+nngB2r BtNonVlOLMWmWVOxn4Sdqc3Fn9fMnf8RnAe6lewy7LO4ekR8W+izTGXOGjFXk6YWaBE5gug30EGeL OmvXZzqacO5hXXmw9mqIWiCyZcRH0amiSvsbLwwPlw9J0BIfPUKVvP9TmrqwRsjx7048MbN8Y0Dv1 PvXSKZg6uj4MhGEOpzww==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4k1W-002YPz-Oa; Fri, 24 Jun 2022 14:11:02 +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 1o4k1T-002YPW-Ch for linux-arm-kernel@lists.infradead.org; Fri, 24 Jun 2022 14:11:00 +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 99B7F62025; Fri, 24 Jun 2022 14:10:58 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 411D6C34114; Fri, 24 Jun 2022 14:10:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656079858; bh=JfDZ0zGL+Oe1Ief4Hf49l5Cfje7PQXWbfGifoymEqus=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uv0kYm11rYc1BRXsN6gCIEhWgJ8xVvLySjbqfZm4Q1KKXx+Gwcmi4tFF+05nrp1uj cxwV/+dbvWA7iJw3KbLSZov3qQg8T99FgojyUnQPAQ5H3kMCo2RGXKdeX8hmcgPw7F nEGvdRQAk2nWbpdDx0bVP6vdKJMojZIGpSCJbljGKzZF1IOXvKRxrOM5JCOZs+ZZkb xj4yJBOfJEPOAXdKtOJf6KRsTOjNv/331rfjXCS0qEa21bHjJ/eg/3CMVSp42LLzIo 7pbEGeZCUwlDAxEFvoNij2jmgwuXK+SAZrC32OastjdUo4uCU5Dt+Mdt0sQpPS1/A+ epW1VXV0WPS9g== Date: Fri, 24 Jun 2022 15:10:46 +0100 From: Will Deacon To: Mark Brown Cc: Catalin Marinas , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64/signal: Clean up SVE/SME feature checking inconsistency Message-ID: <20220624141046.GA19170@willie-the-truck> References: <20220613210133.1327091-1-broonie@kernel.org> <20220623174737.GA17439@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-20220624_071059_501066_829731A2 X-CRM114-Status: GOOD ( 14.81 ) 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, Jun 24, 2022 at 02:28:07PM +0100, Mark Brown wrote: > On Thu, Jun 23, 2022 at 06:47:38PM +0100, Will Deacon wrote: > > > This breaks the allnoconfig build for me: > > > ld.lld: error: undefined symbol: restore_sve_fpsimd_context > > >>> referenced by signal.c > > >>> kernel/signal.o:(__arm64_sys_rt_sigreturn) in archive arch/arm64/built-in.a > > make: *** [Makefile:1164: vmlinux] Error 1 > > I can't reproduce that here - could you confirm exactly what tree you > applied against and what toolchain you're using? I'm normally using > clang 15 at the minute, 14 seems fine too, and applied against both > -next and v5.19-rc3 all of which are building an allnoconfig happily for > me. I can reproduce the issue with just this patch applied on top of -rc3. I'll give your v2 a try, bu FWIW I'm using clang 12.0.6 and building using: $ make LLVM=1 ARCH=arm64 mrproper allnoconfig $ make LLVM=1 ARCH=arm64 -j100 Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel