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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DABAEE49A0 for ; Wed, 23 Aug 2023 06:59:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233056AbjHWG7g (ORCPT ); Wed, 23 Aug 2023 02:59:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48100 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231194AbjHWG7f (ORCPT ); Wed, 23 Aug 2023 02:59:35 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5C279CE3; Tue, 22 Aug 2023 23:59:34 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id DF78261044; Wed, 23 Aug 2023 06:59:33 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C9F75C433C8; Wed, 23 Aug 2023 06:59:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1692773973; bh=Nb5NOLMCbzrJX2FpremlVeT/Pn2TmlTfjHH3zhMBlVo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=baXqW9D/x7mqIxT04bR8D7YS/EpFiAeSSufKKGHltxhzDeJl5YbiiE3qQcMR6iWDL BfC+0brQB7Mtu5zt4/lYbHTOEB3MGg0q1fgygt6V/NalvylqlaBK99iFlBv9PTOZF5 wXDud0DVZhpo4GcafBXOo02+Njp77A4/2HCc4jz3iavegL1XCWkyCvJO9qXM6NiNKE XNCTUZbyPczjPTpSZ6xdokmH0Y03WgWtHcsVvskeXq58tOv2KDWK/IhLXA8x6pJY48 omjBXXqgmSF5hAg1q8aZYb5Ge8aZ60OmVl5hLwlK6u44BjZ2PBCrq9B55MUJn/DFN3 DKrg0+tNM97ew== From: =?utf-8?B?QmrDtnJuIFTDtnBlbA==?= To: Randy Dunlap , Stephen Rothwell , Linux Next Mailing List Cc: Linux Kernel Mailing List , linux-riscv Subject: Re: linux-next: Tree for Aug 21 (riscv-64 asm) In-Reply-To: <0111b49a-8cdf-2c1a-bab3-d1fd647aafa6@infradead.org> References: <20230821164605.7bac05f1@canb.auug.org.au> <5ebf04f8-0cf6-d2b4-fb73-f51fff421b3a@infradead.org> <87ttsr33a8.fsf@all.your.base.are.belong.to.us> <0111b49a-8cdf-2c1a-bab3-d1fd647aafa6@infradead.org> Date: Wed, 23 Aug 2023 08:59:30 +0200 Message-ID: <87bkeyxmzx.fsf@all.your.base.are.belong.to.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org Randy Dunlap writes: > Hi, > > On 8/22/23 01:11, Bj=C3=B6rn T=C3=B6pel wrote: >> Randy Dunlap writes: >>=20 >>> On 8/20/23 23:46, Stephen Rothwell wrote: >>>> Hi all, >>>> >>>> Changes since 20230818: >>>> >>> >>> ../arch/riscv/kernel/traps.c: In function 'do_irq': >>> ../arch/riscv/kernel/traps.c:384:1: error: s0 cannot be used in 'asm' h= ere >>> 384 | } >>> | ^ >>> ../arch/riscv/kernel/irq.c: In function 'do_softirq_own_stack': >>> ../arch/riscv/kernel/irq.c:94:1: error: s0 cannot be used in 'asm' here >>> 94 | } >>> | ^ >>> >>> >>> 2 out of 10 risc-v 64-bit builds failed with these errors. >>> >>> Is this a toolchain problem or something else? >>=20 >> Hmm, do you have a link to config/toolchain/log, or similar? > > The full randconfig file is attached. > > The toolchain is Arnd's build of gcc 13.1.0 from: > https://mirrors.edge.kernel.org/pub/tools/crosstool/ > (x86_64 host) > > Hm, I see that the latest/current there is gcc 13.2.0. > I'll upgrade later today. Thanks Randy! I can reproduce with GCC 12 on my machine. The config has | # CONFIG_FRAME_POINTER is not set but for some reason "-fno-omit-frame-pointer" is passed to GCC anyway, which is why GCC complains about s0 (FP on RISC-V) in asm. I'll dig a bit more. Bj=C3=B6rn