From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (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 512F53624A1 for ; Fri, 6 Feb 2026 12:24:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.67.36.65 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770380663; cv=none; b=p4EjvWIlKuYsti0KEh5TQl/L86tHWhsLYqqw3JXioKkbKd7bk86wGYl3xLmC0LTw4MDoVaNGZnViVB+UqjbnFR8BlKwQ4TbNpfOM3YuxAa2J9Oo00RDrzMkxALFdiYKw0M97CnkLY2e8oC7hEcyh8aIxjIkBTuDvPSsSFWhqh20= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770380663; c=relaxed/simple; bh=xihRajkhxSN0LzS6oaE2l+KPnSf/jZpWp5DiMy2CGUs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=DIunD6fNx8cuuL5I1bAlA7Paqk2eStIQxCdxFNE9Cu9yr7xhjiUonuac/+j+qjO3NGdlieIHGk2UVl1IhZtZfqO2piBv8YgSVMKsJdYteuzLAErzHqBQZewNiidrnKZX/HL/g1gqc+k3RDrLdYa2/2OKT3mZGD1Ryg59FNntuvY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.net; spf=pass smtp.mailfrom=posteo.net; dkim=pass (2048-bit key) header.d=posteo.net header.i=@posteo.net header.b=NmHEMIco; arc=none smtp.client-ip=185.67.36.65 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=posteo.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=posteo.net header.i=@posteo.net header.b="NmHEMIco" Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 9026224002A for ; Fri, 6 Feb 2026 13:24:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.net; s=2017; t=1770380656; bh=U+Pf4h9M3YEQg0wRE4TDVLhds2dAi1ljJ/3l0LMHbzg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=NmHEMIcoerHjzuD4tJMyvxsXu9zwDiXUTVm/LEGhC8+I9Ssm8IEcX3p/fpIQqzDhI +hGqZvk61EpnBPX45I4KE0MQAENUK3bA1RmGtJLEtlekWDwWOqyERmJlHDFIaRY2DS Lccl46s+Tc1RjhTQayH+mTu39OlRxE2bdHlqE/Gjjjm/6J3o8xEjxZzqD+nhGBxGdh D9MBSNchx+HlNaM4jNlh3H3dQRolnzWG9e/IjZypcEAJK911ajBH/QSF0EJKENjDVh 5EBI3kinb27Nmh9rgH13fXL2Q539V0/vxhKn7V/cfMwYj65vHOUctzBW7YVjY6u2Dk mPbITL76tJr7g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4f6tYh12xGz9rxF; Fri, 6 Feb 2026 13:24:08 +0100 (CET) From: Charalampos Mitrodimas To: Asuna Yang Cc: Nathan Chancellor , Nicolas Schier , Miguel Ojeda , Boqun Feng , Gary Guo , =?utf-8?Q?Bj=C3=B6rn?= Roy Baron , Benno Lossin , Andreas Hindborg , Alice Ryhl , Trevor Gross , Danilo Krummrich , Nick Desaulniers , Bill Wendling , Justin Stitt , Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , Jonathan Corbet , Conor Dooley , Mingcong Bai , Han Gao , Vivian Wang , Jason Montleon , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, llvm@lists.linux.dev, linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org Subject: Re: [PATCH v6 4/4] RISC-V: handle extension configs for bindgen, re-enable gcc + rust builds In-Reply-To: <9323714a-b15f-4616-a525-780accf33b52@isrc.iscas.ac.cn> References: <20251230-gcc-rust-v5-v6-0-2ac86ba728c8@isrc.iscas.ac.cn> <20251230-gcc-rust-v5-v6-4-2ac86ba728c8@isrc.iscas.ac.cn> <87v7gk8r5x.fsf@posteo.net> <9323714a-b15f-4616-a525-780accf33b52@isrc.iscas.ac.cn> Date: Fri, 06 Feb 2026 12:24:15 +0000 Message-ID: <874inucb6g.fsf@posteo.net> Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Asuna Yang writes: > On 1/29/26 21:49, Charalampos Mitrodimas wrote: > >> I'm under the impression that the `!RUST ||` guard here doesn't >> actually prevent the `$(bindgen-backend-option,...)` call from being >> executed. `$(...)` shell expansions should happen during the textual >> substitution phase, before symbol dependency evaluation occurs, check >> documentation at kconfig-macro-language.rst lines 228-229. > > I suppose this is unavoidable if we decide to probe options rather > than rely on version numbers. > > Similar issue also occurs in `cc-option`, for example: > > depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64imv) > depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32imv) > > For 64-bit builds, `-march=rv32imv` will still be probed; for 32-bit > builds, `-march=rv64imv` will still be probed. > > I agree with Nathan that this trivial waste is worth it for the sake > of simplicity. Understood. Seems not worth it at all. > > Best regards, > Asuna