On 9/18/24 07:14, LIU Zhiwei wrote:
On 2024/9/12 2:34, Richard Henderson wrote:
On 9/11/24 06:26, LIU Zhiwei wrote:
While the compiler doesn't support RISCV_HWPROBE_EXT_ZVE64X,
we use RISCV_HWPROBE_IMA_V instead.
Language is incorrect here. The compiler has nothing to do with it.
Perhaps "I
On 2024/9/12 2:34, Richard Henderson wrote:
On 9/11/24 06:26, LIU Zhiwei wrote:
While the compiler doesn't support RISCV_HWPROBE_EXT_ZVE64X,
we use RISCV_HWPROBE_IMA_V instead.
Language is incorrect here. The compiler has nothing to do with it.
Perhaps "If the installed kernel header files
On 9/11/24 06:26, LIU Zhiwei wrote:
While the compiler doesn't support RISCV_HWPROBE_EXT_ZVE64X,
we use RISCV_HWPROBE_IMA_V instead.
Language is incorrect here. The compiler has nothing to do with it.
Perhaps "If the installed kernel header files do not support...".
However, if you use only R
From: TANG Tiancheng
Add support for probing RISC-V vector extension availability in
the backend. This information will be used when deciding whether
to use vector instructions in code generation.
Cache lg2(vlenb) for the backend. The storing of lg2(vlenb) means
we can convert all of the divisio
