On 9/27/23 11:48, Joern Rennecke wrote:
Regression tested for:
riscv-sim
riscv-sim/-march=rv32gcv_zfh/-mabi=ilp32d/-ftree-vectorize/--param=riscv-autovec-preference=scalable
riscv-sim/-march=rv32imac/-mabi=ilp32
riscv-sim/-march=rv64gcv_zfh_zvfh_zba_zbb_zbc_zicond_zicboz_
Hi Joern.
> Hmm, you are right. I personally prefer my version because it allows
> consistent naming of the
> different tests, also easily extendible when new extensions need testing.
> Although the riscv_vector name has the advantage that it is better
> legible for people who are
> not used to d
On Tue, 1 Aug 2023 at 14:44, Robin Dapp wrote:
>
> Hi Joern,
>
> thanks, I believe this will help with testing.
>
> > +proc check_effective_target_riscv_v { } {
> > +return [check_no_compiler_messages riscv_ext_v assembly {
> > + #ifndef __riscv_v
> > + #error "Not __riscv_v"
> > +
Hi Joern,
thanks, I believe this will help with testing.
> +proc check_effective_target_riscv_v { } {
> +return [check_no_compiler_messages riscv_ext_v assembly {
> + #ifndef __riscv_v
> + #error "Not __riscv_v"
> + #endif
> +}]
> +}
This can be replaced by riscv_vector
This makes it easier to write tests that safely test features needing
d, v and/or zfh extensions.
check_effective_target_riscv_v checks if the current target allows to
use vector instructions.
add_options_for_riscv_v ask to add an -arch option to change the
target to one like the current one, but
