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 69BA5C61DA3 for ; Tue, 21 Feb 2023 22:33:49 +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=VBB5j1ro8q+5myCEwbd4dmqLUHotWLHxbc4MQnws5yw=; b=V6dUGDkpDc7Bz4 bnHMtV4GHeuNY1fYk5z78CPtD5yikN/Jk0AMO/wyJeZZzGFwzG2Vu2vC2z63Py50RNJLDaIpQFTw2 /Mk0gEZNHaAIWWuyeNiK6c2gqX4KsTEfQHMKTs4CK7u4up1D9T8hfQEPPk784r5fUgg6rkp9KfDhZ qm6Up1YKH7JZR/tyJhXwyzND+VAI8iTvfV4uehi62OjICzb8e4khSu4Jz4No9yNm8N6g0HrtzN4lW GxdBcNKSoSQB5j0zWb/UZ0O8CsBdLc+cHFJODz0OKyC01gV02KMrKjO66g7jBdTPqOk+SqiKsrVju 9Oo+YQWfQyIeHSgtA0kw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pUbCf-00A076-Dm; Tue, 21 Feb 2023 22:33:41 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pUbCa-00A06E-1e for linux-riscv@lists.infradead.org; Tue, 21 Feb 2023 22:33:39 +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 ams.source.kernel.org (Postfix) with ESMTPS id A76ABB810FB; Tue, 21 Feb 2023 22:33:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C91A7C433EF; Tue, 21 Feb 2023 22:33:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1677018813; bh=bhXxhbEaEnMf8ZbGJA8+1NxgqqmQSzTnoWAE5jD/z6k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YVzmVHC2Mo9UUrN5K2TNb49Gqxw9oXP8BcGJThwDJMllEgZ91pbLbLBT/9WqjPotG zcXv+DyOXkZXUK2CqaOfZg77KLmS7hp6dg7iqm4D59SMfdVAolDcJ6Cv4mpJh2o3kc 8YmjMz18+B1z/6IrOgOdiAUHWmfgGT3Pc23L0fwXrmQme02Zsz82VaozJfB0TCrcCp hRTAVUWb6dkq8ioxGhApimK3tMyzrujU5fozZ8ffMLDKVcen05MS6MSTBV+BZA2EuA BaZrKGJjvZEDsLevE7rDdpG4LUhmIvJwphkJxxRamcB+wfTaorGAf5QXPQx2rQ/DjG PuTOQrIWoocOQ== Date: Tue, 21 Feb 2023 15:33:31 -0700 From: Nathan Chancellor To: Conor Dooley Cc: Naresh Kamboju , llvm@lists.linux.dev, linux-riscv , linux-stable , lkft-triage@lists.linaro.org, Greg Kroah-Hartman , Sasha Levin , conor@kernel.org, Heiko Stuebner Subject: Re: stable-rc: 5.10: riscv: defconfig: clang-nightly: build failed - Invalid or unknown z ISA extension: 'zifencei' Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230221_143336_404143_98482FEB X-CRM114-Status: GOOD ( 17.96 ) X-BeenThere: linux-riscv@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-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On Tue, Feb 21, 2023 at 09:15:11AM +0000, Conor Dooley wrote: > On Tue, Feb 21, 2023 at 02:30:17PM +0530, Naresh Kamboju wrote: > > The riscv defconfig and tinyconfig builds failed with clang-nightly > > due to below build warnings / errors on latest stable-rc 5.10. > > > > Regression on riscv: > > - build/clang-nightly-tinyconfig - FAILED > > - build/clang-nightly-defconfig - FAILED > > > Build log: > > ---- > > make --silent --keep-going --jobs=8 > > O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=riscv > > CROSS_COMPILE=riscv64-linux-gnu- HOSTCC=clang CC=clang LLVM=1 > > LLVM_IAS=1 LD=riscv64-linux-gnu-ld > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/version.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/do_mounts.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/noinitramfs.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/calibrate.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > > Build details, > > https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.168-58-g7d11e4c4fc56/testrun/14869376/suite/build/test/clang-nightly-tinyconfig/details/ > > binutils 2.35 by the looks of things, I **think** that zifencei didn't > land until 2.36. zicsr and zifence get added via cc-option-yn, which, > IIRC, doesn't do anything with the linker. I dunno if anyone in RISC-V > land cares this much about "odd" configurations back in 5.10, but while > a fix is outstanding, you could use a newer binutils? This is new in clang-17 so I bisected LLVM down to commit 22e199e6afb1 ("[RISCV] Accept zicsr and zifencei command line options"), so I think we need something like commit aae538cd03bc ("riscv: fix detection of toolchain Zihintpause support") for zifencei to make sure all three tools stay in sync, since I suspect that this is reproducible in mainline with GNU ld. We just happen not to notice when using LLVM=1 LLVM_IAS=1 since the tools have symmetrical support. I can work up something like that change tomorrow if that seems like the path worth taking. Cheers, Nathan _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B9942EA4 for ; Tue, 21 Feb 2023 22:33:33 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C91A7C433EF; Tue, 21 Feb 2023 22:33:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1677018813; bh=bhXxhbEaEnMf8ZbGJA8+1NxgqqmQSzTnoWAE5jD/z6k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YVzmVHC2Mo9UUrN5K2TNb49Gqxw9oXP8BcGJThwDJMllEgZ91pbLbLBT/9WqjPotG zcXv+DyOXkZXUK2CqaOfZg77KLmS7hp6dg7iqm4D59SMfdVAolDcJ6Cv4mpJh2o3kc 8YmjMz18+B1z/6IrOgOdiAUHWmfgGT3Pc23L0fwXrmQme02Zsz82VaozJfB0TCrcCp hRTAVUWb6dkq8ioxGhApimK3tMyzrujU5fozZ8ffMLDKVcen05MS6MSTBV+BZA2EuA BaZrKGJjvZEDsLevE7rDdpG4LUhmIvJwphkJxxRamcB+wfTaorGAf5QXPQx2rQ/DjG PuTOQrIWoocOQ== Date: Tue, 21 Feb 2023 15:33:31 -0700 From: Nathan Chancellor To: Conor Dooley Cc: Naresh Kamboju , llvm@lists.linux.dev, linux-riscv , linux-stable , lkft-triage@lists.linaro.org, Greg Kroah-Hartman , Sasha Levin , conor@kernel.org, Heiko Stuebner Subject: Re: stable-rc: 5.10: riscv: defconfig: clang-nightly: build failed - Invalid or unknown z ISA extension: 'zifencei' Message-ID: References: Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Feb 21, 2023 at 09:15:11AM +0000, Conor Dooley wrote: > On Tue, Feb 21, 2023 at 02:30:17PM +0530, Naresh Kamboju wrote: > > The riscv defconfig and tinyconfig builds failed with clang-nightly > > due to below build warnings / errors on latest stable-rc 5.10. > > > > Regression on riscv: > > - build/clang-nightly-tinyconfig - FAILED > > - build/clang-nightly-defconfig - FAILED > > > Build log: > > ---- > > make --silent --keep-going --jobs=8 > > O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=riscv > > CROSS_COMPILE=riscv64-linux-gnu- HOSTCC=clang CC=clang LLVM=1 > > LLVM_IAS=1 LD=riscv64-linux-gnu-ld > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/version.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/do_mounts.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/noinitramfs.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > riscv64-linux-gnu-ld: failed to merge target specific data of file > > init/calibrate.o > > riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_zicsr2p0_zifencei2p0: > > Invalid or unknown z ISA extension: 'zifencei' > > > Build details, > > https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.168-58-g7d11e4c4fc56/testrun/14869376/suite/build/test/clang-nightly-tinyconfig/details/ > > binutils 2.35 by the looks of things, I **think** that zifencei didn't > land until 2.36. zicsr and zifence get added via cc-option-yn, which, > IIRC, doesn't do anything with the linker. I dunno if anyone in RISC-V > land cares this much about "odd" configurations back in 5.10, but while > a fix is outstanding, you could use a newer binutils? This is new in clang-17 so I bisected LLVM down to commit 22e199e6afb1 ("[RISCV] Accept zicsr and zifencei command line options"), so I think we need something like commit aae538cd03bc ("riscv: fix detection of toolchain Zihintpause support") for zifencei to make sure all three tools stay in sync, since I suspect that this is reproducible in mainline with GNU ld. We just happen not to notice when using LLVM=1 LLVM_IAS=1 since the tools have symmetrical support. I can work up something like that change tomorrow if that seems like the path worth taking. Cheers, Nathan