(attempt to) Fix RISC-V toolchain extension support detection
cover (attempt to) Fix RISC-V toolchain extension support detection
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.
Our current checks for extension support only cover the compiler, but it appears to me that we need to check both the compiler & linker support in case of "pot-luck" configurations that mix different versions of LD,AS,CC etc.
Linker support does not seem possible to actually check, since the ISA string is emitted into the object files - so I put in version checks for that. The checks have gotten a bit ugly since 32 & 64 bit support need to be checked independently but ahh well.
As I was going, I fell into the trap of there being duplicated checks for CC support in both the Makefile and Kconfig, so as part of renaming the Kconfig symbol to TOOLCHAIN_HAS_FOO, I dropped the extra checks in the Makefile. This has the added advantage of the TOOLCHAIN_HAS_FOO symbol for Zihintpause appearing in .config.
I pushed out a version of this that specificly checked for assember support for LKP to test & it looked /okay/ - but I did some more testing today and realised that this is redudant & have since dropped the as check.
I tested locally with a fair few different combinations, to try and cover each of AS, LD, CC missing support for the extension.
The one that I am left wondering about is Zicsr/Zifencei. Our Makefile has:
Quoted 4 lines
# Newer binutils versions default to ISA spec version 20191213 which moves some
# instructions from the I extension to the Zicsr and Zifencei extensions. toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei
I'd like to also move that one to Kconfig rather than the Makefile so that, again, it shows up in .config etc. But as Zicsr/Zifencei do not appear to be emitted into the object files it's not a fix and can be a follow-on patch if my approach here is not entirely off-the-wall.
I am not 100% on the LD/LLD versions that I picked, I went off of a git branch -a --contains of the first commits I found that with mention of the extension. Please scream if I got it wrong, I'm not overly familar with where to find this sort of info for the toolchains.
Thanks,
Conor.
Conor Dooley (2):
riscv: fix detection of toolchain Zicbom support
riscv: fix detection of toolchain Zihintpause support
arch/riscv/Kconfig | 17 +++++++++++++---- arch/riscv/Makefile | 6 ++---- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 16 insertions(+), 9 deletions(-)
Signature · 1 line
2.37.3
PATCH 1/2 riscv: fix detection of toolchain Zicbom support
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zicbom but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zicbom1p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zicbom'
Convert CC_HAS_ZICBOM to TOOLCHAIN_HAS_ZICBOM & check if the linker also supports Zicbom.
--- arch/riscv/Kconfig | 10 ++++++---- arch/riscv/Makefile | 3 +-- 2 files changed, 7 insertions(+), 6 deletions(-)
arch/riscv/Kconfig +6 -4
@@ -401,14 +401,16 @@ config RISCV_ISA_SVPBMT If you don't know what to do here, say Y. -config CC_HAS_ZICBOM +config TOOLCHAIN_HAS_ZICBOM bool - default y if 64BIT && $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) - default y if 32BIT && $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23900 config RISCV_ISA_ZICBOM bool "Zicbom extension support for non-coherent DMA operation" - depends on CC_HAS_ZICBOM + depends on TOOLCHAIN_HAS_ZICBOM depends on !XIP_KERNEL && MMU select RISCV_DMA_NONCOHERENT select RISCV_ALTERNATIVE
arch/riscv/Makefile +1 -2
@@ -57,8 +57,7 @@ toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zi riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei # Check if the toolchain supports Zicbom extension -toolchain-supports-zicbom := $(call cc-option-yn, -march=$(riscv-march-y)_zicbom) -riscv-march-$(toolchain-supports-zicbom) := $(riscv-march-y)_zicbom +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause)
Signature · 1 line
2.37.3
Re: [PATCH 1/2] riscv: fix detection of toolchain Zicbom support
Hi Conor,
Am Donnerstag, 6. Oktober 2022, 19:35:20 CEST schrieb Conor Dooley:
Quoted 29 lines
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zicbom but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zicbom1p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zicbom'
Convert
CC_HAS_ZICBOMtoTOOLCHAIN_HAS_ZICBOM& check if the linker also supports Zicbom.Reported-by Kevin Hilman <[email protected]>Fixes 1631ba1259d6 ("riscv: Add support for non-coherent devices using zicbom extension")Signed-off-by Conor Dooley <[email protected]>--- arch/riscv/Kconfig | 10 ++++++---- arch/riscv/Makefile | 3 +-- 2 files changed, 7 insertions(+), 6 deletions(-)arch/riscv/Kconfig +0
-0@@ -401,14 +401,16 @@ config RISCV_ISA_SVPBMT If you don't know what to do here, say Y.
arch/riscv/Kconfig config RISCV_ISA_SVPBMT · line 409
Quoted 10 lines
arch/riscv/Kconfig +5
-3-config CC_HAS_ZICBOM +config TOOLCHAIN_HAS_ZICBOM bool - default y if 64BIT && $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) - default y if 32BIT && $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23900
I did needed to look quite closely at the cc-option-voodoo, but it really seems to work out as expected :-)
I can't say much to the specific L(L)D_VERSION values but the change itself looks good, so
Quoted 14 lines
arch/riscv/Kconfig +1
-1config RISCV_ISA_ZICBOM bool "Zicbom extension support for non-coherent DMA operation" - depends on CC_HAS_ZICBOM + depends on TOOLCHAIN_HAS_ZICBOM depends on !XIP_KERNEL && MMU select RISCV_DMA_NONCOHERENT select RISCV_ALTERNATIVEarch/riscv/Makefile +0
-0
arch/riscv/Makefile toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zi · line 63
Quoted 9 lines
arch/riscv/Makefile +1
-2@@ -57,8 +57,7 @@ toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zi riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei # Check if the toolchain supports Zicbom extension -toolchain-supports-zicbom := $(call cc-option-yn, -march=$(riscv-march-y)_zicbom) -riscv-march-$(toolchain-supports-zicbom) := $(riscv-march-y)_zicbom +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause)
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Re: [PATCH 1/2] riscv: fix detection of toolchain Zicbom support
In reply to Conor DooleyQuoted 9 lines · Conor Dooley
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zicbom but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zicbom1p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zicbom'
Quoted 8 lines
Convert
CC_HAS_ZICBOMtoTOOLCHAIN_HAS_ZICBOM& check if the linker also supports Zicbom.Reported-by Kevin Hilman <[email protected]>Fixes 1631ba1259d6 ("riscv: Add support for non-coherent devices using zicbom extension")Signed-off-by Conor Dooley <[email protected]>
The versions look correct to me. I see the LLVM zicbom commit [1] in llvmorg-15.0.0 and I see the binutils zicbom commit [2] in binutils-2_39.
FWIW, if we are adding explicit tool versions to the Kconfig, could you not also drop the cc-option checks? Typically, cc-option is only used when dynamically checking for a feature, in lieu of statically checking a version. No strong opinion though.
[1]: https://github.com/llvm/llvm-project/commit/4f40ca53cefb725aca6564585d0ec4836a79e21a
[2]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=41d6ac5da655a2e78109848f2db47e53552fd61a
Quoted 48 lines
--- arch/riscv/Kconfig | 10 ++++++---- arch/riscv/Makefile | 3 +-- 2 files changed, 7 insertions(+), 6 deletions(-)arch/riscv/Kconfig +6
-4@@ -401,14 +401,16 @@ config RISCV_ISA_SVPBMT If you don't know what to do here, say Y. -config CC_HAS_ZICBOM +config TOOLCHAIN_HAS_ZICBOM bool - default y if 64BIT && $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) - default y if 32BIT && $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23900 config RISCV_ISA_ZICBOM bool "Zicbom extension support for non-coherent DMA operation" - depends on CC_HAS_ZICBOM + depends on TOOLCHAIN_HAS_ZICBOM depends on !XIP_KERNEL && MMU select RISCV_DMA_NONCOHERENT select RISCV_ALTERNATIVEarch/riscv/Makefile +1
-2@@ -57,8 +57,7 @@ toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zi riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei # Check if the toolchain supports Zicbom extension -toolchain-supports-zicbom := $(call cc-option-yn, -march=$(riscv-march-y)_zicbom) -riscv-march-$(toolchain-supports-zicbom) := $(riscv-march-y)_zicbom +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause)Signature · 1 line
2.37.3
Re: [PATCH 1/2] riscv: fix detection of toolchain Zicbom support
Quoted 19 lines · Nathan Chancellor
Quoted 9 lines · Conor Dooley
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zicbom but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zicbom1p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zicbom'
Quoted 8 lines
Convert
CC_HAS_ZICBOMtoTOOLCHAIN_HAS_ZICBOM& check if the linker also supports Zicbom.Reported-by Kevin Hilman <[email protected]>Fixes 1631ba1259d6 ("riscv: Add support for non-coherent devices using zicbom extension")Signed-off-by Conor Dooley <[email protected]>
Quoted 8 lines
The versions look correct to me. I see the LLVM zicbom commit [1] in llvmorg-15.0.0 and I see the binutils zicbom commit [2] in binutils-2_39.
FWIW, if we are adding explicit tool versions to the
Kconfig, could you not also drop the cc-option checks? Typically, cc-option is only used when dynamically checking for a feature, in lieu of statically checking a version. No strong opinion though.
Ehh, the explicit version checks are for linker support, but it could be that your linker supports it but other things do not. The compilers support can still be checked with cc-option, no?
This error here happens when the compiler does support it, so the string containing zicbom is emitted in the object files. That can't be checked dynamically. For the opposite situation, dynamic checking is possible so I tried retained them. If it's convention to do one or the other, I can easily switch.
I'm out of my comfort zone when it comes to kbuild plumbing so please, please lmk if I'm missing something...
Quoted 54 lines
Reviewed-by Nathan Chancellor <[email protected]>[1]: https://github.com/llvm/llvm-project/commit/4f40ca53cefb725aca6564585d0ec4836a79e21a
[2]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=41d6ac5da655a2e78109848f2db47e53552fd61aQuoted 48 lines
--- arch/riscv/Kconfig | 10 ++++++---- arch/riscv/Makefile | 3 +-- 2 files changed, 7 insertions(+), 6 deletions(-)arch/riscv/Kconfig +6
-4@@ -401,14 +401,16 @@ config RISCV_ISA_SVPBMT If you don't know what to do here, say Y. -config CC_HAS_ZICBOM +config TOOLCHAIN_HAS_ZICBOM bool - default y if 64BIT && $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) - default y if 32BIT && $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23900 config RISCV_ISA_ZICBOM bool "Zicbom extension support for non-coherent DMA operation" - depends on CC_HAS_ZICBOM + depends on TOOLCHAIN_HAS_ZICBOM depends on !XIP_KERNEL && MMU select RISCV_DMA_NONCOHERENT select RISCV_ALTERNATIVEarch/riscv/Makefile +1
-2@@ -57,8 +57,7 @@ toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zi riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei # Check if the toolchain supports Zicbom extension -toolchain-supports-zicbom := $(call cc-option-yn, -march=$(riscv-march-y)_zicbom) -riscv-march-$(toolchain-supports-zicbom) := $(riscv-march-y)_zicbom +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause)Signature · 1 line
2.37.3
Re: [PATCH 1/2] riscv: fix detection of toolchain Zicbom support
Quoted 33 lines · Conor Dooley
Quoted 19 lines · Nathan Chancellor
Quoted 9 lines · Conor Dooley
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zicbom but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zicbom1p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zicbom'
Quoted 8 lines
Convert
CC_HAS_ZICBOMtoTOOLCHAIN_HAS_ZICBOM& check if the linker also supports Zicbom.Reported-by Kevin Hilman <[email protected]>Fixes 1631ba1259d6 ("riscv: Add support for non-coherent devices using zicbom extension")Signed-off-by Conor Dooley <[email protected]>Quoted 8 lines
The versions look correct to me. I see the LLVM zicbom commit [1] in llvmorg-15.0.0 and I see the binutils zicbom commit [2] in binutils-2_39.
FWIW, if we are adding explicit tool versions to the
Kconfig, could you not also drop the cc-option checks? Typically, cc-option is only used when dynamically checking for a feature, in lieu of statically checking a version. No strong opinion though.Ehh, the explicit version checks are for linker support, but it could be that your linker supports it but other things do not. The compilers support can still be checked with cc-option, no?
Quoted 8 lines
This error here happens when the compiler does support it, so the string containing zicbom is emitted in the object files. That can't be checked dynamically. For the opposite situation, dynamic checking is possible so I tried retained them. If it's convention to do one or the other, I can easily switch.
I'm out of my comfort zone when it comes to kbuild plumbing so please, please lmk if I'm missing something...
No, you are absolutely correct. That's what I get for reviewing changes right after being off for a week ;) the cc-option checks should remain in addition to the new linker checks, so please disregard that feedback on both changes.
Quoted 54 lines
Quoted 54 lines
Reviewed-by Nathan Chancellor <[email protected]>[1]: https://github.com/llvm/llvm-project/commit/4f40ca53cefb725aca6564585d0ec4836a79e21a
[2]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=41d6ac5da655a2e78109848f2db47e53552fd61aQuoted 48 lines
--- arch/riscv/Kconfig | 10 ++++++---- arch/riscv/Makefile | 3 +-- 2 files changed, 7 insertions(+), 6 deletions(-)arch/riscv/Kconfig +6
-4@@ -401,14 +401,16 @@ config RISCV_ISA_SVPBMT If you don't know what to do here, say Y. -config CC_HAS_ZICBOM +config TOOLCHAIN_HAS_ZICBOM bool - default y if 64BIT && $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) - default y if 32BIT && $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicbom) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicbom) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23900 config RISCV_ISA_ZICBOM bool "Zicbom extension support for non-coherent DMA operation" - depends on CC_HAS_ZICBOM + depends on TOOLCHAIN_HAS_ZICBOM depends on !XIP_KERNEL && MMU select RISCV_DMA_NONCOHERENT select RISCV_ALTERNATIVEarch/riscv/Makefile +1
-2@@ -57,8 +57,7 @@ toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zi riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei # Check if the toolchain supports Zicbom extension -toolchain-supports-zicbom := $(call cc-option-yn, -march=$(riscv-march-y)_zicbom) -riscv-march-$(toolchain-supports-zicbom) := $(riscv-march-y)_zicbom +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause)Signature · 1 line
2.37.3
PATCH 2/2 riscv: fix detection of toolchain Zihintpause support
In reply to Conor DooleyFrom: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zihintpause but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zihintpause'
Add a TOOLCHAIN_HAS_ZIHINTPAUSE which checks if each of the compiler, assembler and linker support the extension. Replace the ifdef in the vdso with one depending on this new symbol.
---
Palmer:
The VDSO change will conflict with Samuel's one, resolution should be trivial.. I only made that change as you warned me about checking for the __riscv_foo stuff if I made the march string depend on the Kconfig entry rather than on the Makefile's cc-option check.
--- arch/riscv/Kconfig | 7 +++++++ arch/riscv/Makefile | 3 +-- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)
arch/riscv/Kconfig +7 -0
@@ -425,6 +425,13 @@ config RISCV_ISA_ZICBOM If you don't know what to do here, say Y. +config TOOLCHAIN_HAS_ZIHINTPAUSE + bool + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zihintpause) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zihintpause) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23600 + config FPU bool "FPU support" default y
arch/riscv/Makefile +1 -2
@@ -60,8 +60,7 @@ riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension -toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause) -riscv-march-$(toolchain-supports-zihintpause) := $(riscv-march-y)_zihintpause +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZIHINTPAUSE) := $(riscv-march-y)_zihintpause KBUILD_CFLAGS += -march=$(subst fd,,$(riscv-march-y)) KBUILD_AFLAGS += -march=$(riscv-march-y)
arch/riscv/include/asm/vdso/processor.h +1 -1
@@ -21,7 +21,7 @@ static inline void cpu_relax(void)* Reduce instruction retirement. * This assumes the PC changes. */ -#ifdef __riscv_zihintpause +#ifdef CONFIG_TOOLCHAIN_HAS_ZIHINTPAUSE __asm__ __volatile__ ("pause" );#else /* Encoding of the pause instruction */
Signature · 1 line
2.37.3
Re: [PATCH 2/2] riscv: fix detection of toolchain Zihintpause support
Am Donnerstag, 6. Oktober 2022, 19:35:21 CEST schrieb Conor Dooley:
Quoted 7 lines
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zihintpause but GNU bintutils 2.35.2 does not, leading build errors like so:
Quoted 8 lines
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zihintpause'
Add a
TOOLCHAIN_HAS_ZIHINTPAUSEwhich checks if each of the compiler, assembler and linker support the extension. Replace the ifdef in the vdso with one depending on this new symbol.Fixes 8eb060e10185 ("arch/riscv: add Zihintpause support")Signed-off-by Conor Dooley <[email protected]>
Re: [PATCH 2/2] riscv: fix detection of toolchain Zihintpause support
In reply to Conor DooleyQuoted 13 lines · Conor Dooley
From: Conor Dooley <[email protected]>
It is not sufficient to check if a toolchain supports a particular extension without checking if the linker supports that extension too. For example, Clang 15 supports Zihintpause but GNU bintutils 2.35.2 does not, leading build errors like so:
riscv64-linux-gnu-ld: -march=rv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0: Invalid or unknown z ISA extension: 'zihintpause'
Add a
TOOLCHAIN_HAS_ZIHINTPAUSEwhich checks if each of the compiler, assembler and linker support the extension. Replace the ifdef in the vdso with one depending on this new symbol.
Quoted 8 lines
Fixes 8eb060e10185 ("arch/riscv: add Zihintpause support")Signed-off-by Conor Dooley <[email protected]>---
Palmer:
The VDSO change will conflict with Samuel's one, resolution should be trivial.. I only made that change as you warned me about checking for the__riscv_foostuff if I made the march string depend on theKconfigentry rather than on the Makefile's cc-option check.
The versions look correct to me. I see the LLVM zihintpause commit [1] in llvmorg-15.0.0 and I see the binutils zihintpause commit [2] in binutils-2_36.
[1]: https://github.com/llvm/llvm-project/commit/005fd8aa702edbc532763038365575da96e5787d
[2]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=aa881ecde48c7a0224b92e2cfa43b37ee9ec9fa2
Similar comment as patch 1, I think we can just drop the cc-option checks. Regardless:
Quoted 55 lines
--- arch/riscv/Kconfig | 7 +++++++ arch/riscv/Makefile | 3 +-- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)arch/riscv/Kconfig +7
-0@@ -425,6 +425,13 @@ config RISCV_ISA_ZICBOM If you don't know what to do here, say Y. +config TOOLCHAIN_HAS_ZIHINTPAUSE + bool + default y + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zihintpause) + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zihintpause) + depends on LLD_VERSION >= 150000 || LD_VERSION >= 23600 + config FPU bool "FPU support" default yarch/riscv/Makefile +1
-2@@ -60,8 +60,7 @@ riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom # Check if the toolchain supports Zihintpause extension -toolchain-supports-zihintpause := $(call cc-option-yn, -march=$(riscv-march-y)_zihintpause) -riscv-march-$(toolchain-supports-zihintpause) := $(riscv-march-y)_zihintpause +riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZIHINTPAUSE) := $(riscv-march-y)_zihintpause KBUILD_CFLAGS += -march=$(subst fd,,$(riscv-march-y)) KBUILD_AFLAGS += -march=$(riscv-march-y)arch/riscv/include/asm/vdso/processor.h +1
-1@@ -21,7 +21,7 @@ static inline void cpu_relax(void)* Reduce instruction retirement. * This assumes the PC changes. */ -#ifdef __riscv_zihintpause +#ifdef CONFIG_TOOLCHAIN_HAS_ZIHINTPAUSE __asm__ __volatile__ ("pause" );#else /* Encoding of the pause instruction */ Signature · 1 line
2.37.3
Quoted 52 lines · Conor Dooley
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.Our current checks for extension support only cover the compiler, but it appears to me that we need to check both the compiler & linker support in case of "pot-luck" configurations that mix different versions of LD,AS,CC etc.
Linker support does not seem possible to actually check, since the ISA string is emitted into the object files - so I put in version checks for that. The checks have gotten a bit ugly since 32 & 64 bit support need to be checked independently but ahh well.
As I was going, I fell into the trap of there being duplicated checks for CC support in both the
MakefileandKconfig, so as part of renaming theKconfigsymbol toTOOLCHAIN_HAS_FOO, I dropped the extra checks in theMakefile. This has the added advantage of theTOOLCHAIN_HAS_FOOsymbol for Zihintpause appearing in .config.I pushed out a version of this that specificly checked for assember support for LKP to test & it looked /okay/ - but I did some more testing today and realised that this is redudant & have since dropped the as check.
I tested locally with a fair few different combinations, to try and cover each of AS, LD, CC missing support for the extension.
The one that I am left wondering about is Zicsr/Zifencei. Our
Makefilehas:Quoted 4 lines
# Newer binutils versions default to ISA spec version 20191213 which moves some
# instructions from the I extension to the Zicsr and Zifencei extensions. toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifenceiI'd like to also move that one to
Kconfigrather than theMakefileso that, again, it shows up in .config etc. But as Zicsr/Zifencei do not appear to be emitted into the object files it's not a fix and can be a follow-on patch if my approach here is not entirely off-the-wall.I am not 100% on the LD/LLD versions that I picked, I went off of a
git branch -a --containsof the first commits I found that with mention of the extension. Please scream if I got it wrong, I'm not overly familar with where to find this sort of info for the toolchains.Thanks,
Conor.
Quoted 12 lines
Conor Dooley (2):
riscv: fix detection of toolchain Zicbom support
riscv: fix detection of toolchain Zihintpause supportarch/riscv/Kconfig | 17 +++++++++++++---- arch/riscv/Makefile | 6 ++---- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 16 insertions(+), 9 deletions(-)Signature · 1 line
2.37.3
This looks good to me, so
For the series
However, we could also drop the compiler and linker checking if we converted our use of cbo.* to the insn-def.h framework (I think Heiko once mentioned looking at doing that, but I'm not sure.) I'm looking at adding Zicboz support right now and for starters I've duplicated and modified these checks. But, I think I'll look into defining the instruction type needed for cbo.* and using insn-def instead.
Thanks,
drew
Quoted 8 lines · Andrew Jones
On Thu, Oct 06, 2022 at 06:35:19PM +0100, Conor Dooley wrote:
However, we could also drop the compiler and linker checking if we converted our use of cbo.* to the
insn-def.hframework (I think Heiko once mentioned looking at doing that, but I'm not sure.) I'm looking at adding Zicboz support right now and for starters I've duplicated and modified these checks. But, I think I'll look into defining the instruction type needed for cbo.* and using insn-def instead.
What is the ETA of your zicboz support? Do you think these patches should be applied to v6.1 & backported before being replaced by insn-def when your zicboz support arrives? Or just wait for your zicboz series?
Trying to decide what status I should set for this in patchwork.
Thanks,
Conor.
Quoted 10 lines · Conor Dooley
Quoted 8 lines · Andrew Jones
On Thu, Oct 06, 2022 at 06:35:19PM +0100, Conor Dooley wrote:
However, we could also drop the compiler and linker checking if we converted our use of cbo.* to the
insn-def.hframework (I think Heiko once mentioned looking at doing that, but I'm not sure.) I'm looking at adding Zicboz support right now and for starters I've duplicated and modified these checks. But, I think I'll look into defining the instruction type needed for cbo.* and using insn-def instead.
Quoted 3 lines
What is the ETA of your zicboz support? Do you think these patches should be applied to v6.1 & backported before being replaced by insn-def when your zicboz support arrives? Or just wait for your zicboz series?
I hope to have something posted by the end of this week, so if all things go well, it could land in 6.1. I think it's reasonable to merge your patches anyway, though, as they fix the current code and we don't know what rabbit holes I may fall in with my series yet.
Thanks,
drew
Quoted 6 lines
Trying to decide what status I should set for this in patchwork.
Thanks,
Conor.
Palmer Dabbelt
maintainerQuoted 39 lines · Conor Dooley
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.Our current checks for extension support only cover the compiler, but it appears to me that we need to check both the compiler & linker support in case of "pot-luck" configurations that mix different versions of LD,AS,CC etc.
Linker support does not seem possible to actually check, since the ISA string is emitted into the object files - so I put in version checks for that. The checks have gotten a bit ugly since 32 & 64 bit support need to be checked independently but ahh well.
As I was going, I fell into the trap of there being duplicated checks for CC support in both the
MakefileandKconfig, so as part of renaming theKconfigsymbol toTOOLCHAIN_HAS_FOO, I dropped the extra checks in theMakefile. This has the added advantage of theTOOLCHAIN_HAS_FOOsymbol for Zihintpause appearing in .config.I pushed out a version of this that specificly checked for assember support for LKP to test & it looked /okay/ - but I did some more testing today and realised that this is redudant & have since dropped the as check.
I tested locally with a fair few different combinations, to try and cover each of AS, LD, CC missing support for the extension.
The one that I am left wondering about is Zicsr/Zifencei. Our
Makefilehas:Quoted 4 lines
# Newer binutils versions default to ISA spec version 20191213 which moves some
# instructions from the I extension to the Zicsr and Zifencei extensions. toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei
Quoted 4 lines
I'd like to also move that one to
Kconfigrather than theMakefileso that, again, it shows up in .config etc. But as Zicsr/Zifencei do not appear to be emitted into the object files it's not a fix and can be a follow-on patch if my approach here is not entirely off-the-wall.
This is actually a different case: for Zicbom and Zihintpause the instructions were added to the toolchain at the same time the extensions were, for Zifencei and Zicsr the toolchain had the instructions before the extension was defined (as they were in previous base ISAs). So the assembler always supports "fence.i", it's just a question of whether it also needs another extension in march.
I'm not opposed to adding a Kconfig for it, but it's a slightly different thing and I'm not sure the Kconfig really helps any because none of the kernel sources need to understand the "the assembler doesn't support the 'fence.i' instruction" case.
Quoted 4 lines
I am not 100% on the LD/LLD versions that I picked, I went off of a
git branch -a --containsof the first commits I found that with mention of the extension. Please scream if I got it wrong, I'm not overly familar with where to find this sort of info for the toolchains.
This LD version check is for the ISA string mismatches between objects? IIRC we stopped failing on those in 2.38, from that point on we just guess at a mix and allow linking anyway (largely because of that fence.i stuff).
Quoted 12 lines
Thanks,
Conor.Conor Dooley (2):
riscv: fix detection of toolchain Zicbom support
riscv: fix detection of toolchain Zihintpause supportarch/riscv/Kconfig | 17 +++++++++++++---- arch/riscv/Makefile | 6 ++---- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 16 insertions(+), 9 deletions(-)
Quoted 45 lines · Palmer Dabbelt
Quoted 39 lines · Conor Dooley
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.Our current checks for extension support only cover the compiler, but it appears to me that we need to check both the compiler & linker support in case of "pot-luck" configurations that mix different versions of LD,AS,CC etc.
Linker support does not seem possible to actually check, since the ISA string is emitted into the object files - so I put in version checks for that. The checks have gotten a bit ugly since 32 & 64 bit support need to be checked independently but ahh well.
As I was going, I fell into the trap of there being duplicated checks for CC support in both the
MakefileandKconfig, so as part of renaming theKconfigsymbol toTOOLCHAIN_HAS_FOO, I dropped the extra checks in theMakefile. This has the added advantage of theTOOLCHAIN_HAS_FOOsymbol for Zihintpause appearing in .config.I pushed out a version of this that specificly checked for assember support for LKP to test & it looked /okay/ - but I did some more testing today and realised that this is redudant & have since dropped the as check.
I tested locally with a fair few different combinations, to try and cover each of AS, LD, CC missing support for the extension.
The one that I am left wondering about is Zicsr/Zifencei. Our
Makefilehas:Quoted 4 lines
# Newer binutils versions default to ISA spec version 20191213 which moves some
# instructions from the I extension to the Zicsr and Zifencei extensions. toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifenceiQuoted 4 lines
I'd like to also move that one to
Kconfigrather than theMakefileso that, again, it shows up in .config etc. But as Zicsr/Zifencei do not appear to be emitted into the object files it's not a fix and can be a follow-on patch if my approach here is not entirely off-the-wall.
Quoted 6 lines
This is actually a different case: for Zicbom and Zihintpause the instructions were added to the toolchain at the same time the extensions were, for Zifencei and Zicsr the toolchain had the instructions before the extension was defined (as they were in previous base ISAs). So the assembler always supports "fence.i", it's just a question of whether it also needs another extension in march.
Yeah, that one isn't going to break the build. If the extra bit isn't emitted then the old linker doesn't care. Was more for whether we wanted it to be consistent with a symbol for everything that we can check easily after the fact.
Quoted 4 lines
I'm not opposed to adding a
Kconfigfor it, but it's a slightly different thing and I'm not sure theKconfigreally helps any because none of the kernel sources need to understand the "the assembler doesn't support the 'fence.i' instruction" case.
tbh beyond the OCD thing about being consistent I don't really care :)
Quoted 8 lines
Quoted 4 lines
I am not 100% on the LD/LLD versions that I picked, I went off of a
git branch -a --containsof the first commits I found that with mention of the extension. Please scream if I got it wrong, I'm not overly familar with where to find this sort of info for the toolchains.This LD version check is for the ISA string mismatches between objects? IIRC we stopped failing on those in 2.38, from that point on we just guess at a mix and allow linking anyway (largely because of that fence.i stuff).
idk, I wouldn't say "mismatches between objects". The _zicbom_zihintpause ends up in the object files and the linker doesnt understand that and aborts. The version checks are so that we don't emitt that string into object files where our linker doesn't support them. It only really matters for people that've got some sort of heavily mixed setup of things - which includes some CIs like Kernel CI.
Quoted 8 lines
Quoted 8 lines
Conor Dooley (2):
riscv: fix detection of toolchain Zicbom support
riscv: fix detection of toolchain Zihintpause supportarch/riscv/Kconfig | 17 +++++++++++++---- arch/riscv/Makefile | 6 ++---- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 16 insertions(+), 9 deletions(-)
Palmer Dabbelt
maintainerQuoted 74 lines · Conor Dooley
Quoted 45 lines · Palmer Dabbelt
Quoted 39 lines · Conor Dooley
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.Our current checks for extension support only cover the compiler, but it appears to me that we need to check both the compiler & linker support in case of "pot-luck" configurations that mix different versions of LD,AS,CC etc.
Linker support does not seem possible to actually check, since the ISA string is emitted into the object files - so I put in version checks for that. The checks have gotten a bit ugly since 32 & 64 bit support need to be checked independently but ahh well.
As I was going, I fell into the trap of there being duplicated checks for CC support in both the
MakefileandKconfig, so as part of renaming theKconfigsymbol toTOOLCHAIN_HAS_FOO, I dropped the extra checks in theMakefile. This has the added advantage of theTOOLCHAIN_HAS_FOOsymbol for Zihintpause appearing in .config.I pushed out a version of this that specificly checked for assember support for LKP to test & it looked /okay/ - but I did some more testing today and realised that this is redudant & have since dropped the as check.
I tested locally with a fair few different combinations, to try and cover each of AS, LD, CC missing support for the extension.
The one that I am left wondering about is Zicsr/Zifencei. Our
Makefilehas:Quoted 4 lines
# Newer binutils versions default to ISA spec version 20191213 which moves some
# instructions from the I extension to the Zicsr and Zifencei extensions. toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifenceiQuoted 4 lines
I'd like to also move that one to
Kconfigrather than theMakefileso that, again, it shows up in .config etc. But as Zicsr/Zifencei do not appear to be emitted into the object files it's not a fix and can be a follow-on patch if my approach here is not entirely off-the-wall.Quoted 6 lines
This is actually a different case: for Zicbom and Zihintpause the instructions were added to the toolchain at the same time the extensions were, for Zifencei and Zicsr the toolchain had the instructions before the extension was defined (as they were in previous base ISAs). So the assembler always supports "fence.i", it's just a question of whether it also needs another extension in march.
Yeah, that one isn't going to break the build. If the extra bit isn't emitted then the old linker doesn't care. Was more for whether we wanted it to be consistent with a symbol for everything that we can check easily after the fact.
Quoted 4 lines
I'm not opposed to adding a
Kconfigfor it, but it's a slightly different thing and I'm not sure theKconfigreally helps any because none of the kernel sources need to understand the "the assembler doesn't support the 'fence.i' instruction" case.tbh beyond the OCD thing about being consistent I don't really care :)
Quoted 8 lines
Quoted 4 lines
I am not 100% on the LD/LLD versions that I picked, I went off of a
git branch -a --containsof the first commits I found that with mention of the extension. Please scream if I got it wrong, I'm not overly familar with where to find this sort of info for the toolchains.This LD version check is for the ISA string mismatches between objects? IIRC we stopped failing on those in 2.38, from that point on we just guess at a mix and allow linking anyway (largely because of that fence.i stuff).
Quoted 6 lines
idk, I wouldn't say "mismatches between objects". The
_zicbom_zihintpauseends up in the object files and the linker doesnt understand that and aborts. The version checks are so that we don't emitt that string into object files where our linker doesn't support them. It only really matters for people that've got some sort of heavily mixed setup of things - which includes some CIs like Kernel CI.
As of 87fdd7ac09b ("RISC-V: Stop reporting warnings for mismatched extension versions"), we should be just ignoring these at link time -- unless I mixed something up and we're still getting errors, in which case we should fix binutils (and then make the check for whatever version that is).
Do you have an example of a link that's failing? I attempted to construct one in the test suite, but not sure if I'm just missing something...
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Conor Dooley (2):
riscv: fix detection of toolchain Zicbom support
riscv: fix detection of toolchain Zihintpause supportarch/riscv/Kconfig | 17 +++++++++++++---- arch/riscv/Makefile | 6 ++---- arch/riscv/include/asm/vdso/processor.h | 2 +- 3 files changed, 16 insertions(+), 9 deletions(-)
Quoted 82 lines · Palmer Dabbelt
Quoted 74 lines · Conor Dooley
Quoted 45 lines · Palmer Dabbelt
Quoted 39 lines · Conor Dooley
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.Our current checks for extension support only cover the compiler, but it appears to me that we need to check both the compiler & linker support in case of "pot-luck" configurations that mix different versions of LD,AS,CC etc.
Linker support does not seem possible to actually check, since the ISA string is emitted into the object files - so I put in version checks for that. The checks have gotten a bit ugly since 32 & 64 bit support need to be checked independently but ahh well.
As I was going, I fell into the trap of there being duplicated checks for CC support in both the
MakefileandKconfig, so as part of renaming theKconfigsymbol toTOOLCHAIN_HAS_FOO, I dropped the extra checks in theMakefile. This has the added advantage of theTOOLCHAIN_HAS_FOOsymbol for Zihintpause appearing in .config.I pushed out a version of this that specificly checked for assember support for LKP to test & it looked /okay/ - but I did some more testing today and realised that this is redudant & have since dropped the as check.
I tested locally with a fair few different combinations, to try and cover each of AS, LD, CC missing support for the extension.
The one that I am left wondering about is Zicsr/Zifencei. Our
Makefilehas:Quoted 4 lines
# Newer binutils versions default to ISA spec version 20191213 which moves some
# instructions from the I extension to the Zicsr and Zifencei extensions. toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifenceiQuoted 4 lines
I'd like to also move that one to
Kconfigrather than theMakefileso that, again, it shows up in .config etc. But as Zicsr/Zifencei do not appear to be emitted into the object files it's not a fix and can be a follow-on patch if my approach here is not entirely off-the-wall.Quoted 6 lines
This is actually a different case: for Zicbom and Zihintpause the instructions were added to the toolchain at the same time the extensions were, for Zifencei and Zicsr the toolchain had the instructions before the extension was defined (as they were in previous base ISAs). So the assembler always supports "fence.i", it's just a question of whether it also needs another extension in march.
Yeah, that one isn't going to break the build. If the extra bit isn't emitted then the old linker doesn't care. Was more for whether we wanted it to be consistent with a symbol for everything that we can check easily after the fact.
Quoted 4 lines
I'm not opposed to adding a
Kconfigfor it, but it's a slightly different thing and I'm not sure theKconfigreally helps any because none of the kernel sources need to understand the "the assembler doesn't support the 'fence.i' instruction" case.tbh beyond the OCD thing about being consistent I don't really care :)
Quoted 8 lines
Quoted 4 lines
I am not 100% on the LD/LLD versions that I picked, I went off of a
git branch -a --containsof the first commits I found that with mention of the extension. Please scream if I got it wrong, I'm not overly familar with where to find this sort of info for the toolchains.This LD version check is for the ISA string mismatches between objects? IIRC we stopped failing on those in 2.38, from that point on we just guess at a mix and allow linking anyway (largely because of that fence.i stuff).
Quoted 6 lines
idk, I wouldn't say "mismatches between objects". The
_zicbom_zihintpauseends up in the object files and the linker doesnt understand that and aborts. The version checks are so that we don't emitt that string into object files where our linker doesn't support them. It only really matters for people that've got some sort of heavily mixed setup of things - which includes some CIs like Kernel CI.
Quoted 7 lines
As of
87fdd7ac09b("RISC-V: Stop reporting warnings for mismatched extension versions"), we should be just ignoring these at link time -- unless I mixed something up and we're still getting errors, in which case we should fix binutils (and then make the check for whatever version that is).Do you have an example of a link that's failing? I attempted to construct one in the test suite, but not sure if I'm just missing something...
Following some discussion on IRC, settling for 2.38 as the gating version for Zicbom as logic was added there to stop erroring at all for unrecognised isa strings in objects as per Palmer's suggestion.
Tested 2.38 w/:CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=120100CONFIG_CLANG_VERSION=0CONFIG_AS_IS_GNU=yCONFIG_AS_VERSION=23900CONFIG_LD_IS_BFD=yCONFIG_LD_VERSION=23800CONFIG_LLD_VERSION=0
and it does link properly. Folding in a 23800 instead of 23900 seems fair enough to me.
Thanks,
Conor.
Palmer Dabbelt
AppliedQuoted 8 lines · Conor Dooley
From: Conor Dooley <[email protected]>
Hey,
This came up due to a report from Kevin @ kernel-ci, who had been running a mixed configuration of GNU binutils and clang. Their compiler was relatively recent & supports Zicbom but binutils @ 2.35.2 did not.[...]
Applied, thanks!
[1/2] riscv: fix detection of toolchain Zicbom support
https://git.kernel.org/palmer/c/b8c86872d1dc [2/2] riscv: fix detection of toolchain Zihintpause support https://git.kernel.org/palmer/c/aae538cd03bc
Best regards,
Signature · 1 line
Palmer Dabbelt <[email protected]>