Palmer: For short-term, this should help your internal test: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1233
On Wed, May 17, 2023 at 10:20 AM Kito Cheng <kito.ch...@sifive.com> wrote: > > Currently we are highly rely on simulator can setup correctly by ELF > attribute or -march setting, but seems not true for everyone, for > longer term we need something like > check_effective_target_aarch64_sve_hw, but as Palmer point out, we > might need...bunch of that for different extensions.... > > On Wed, May 17, 2023 at 10:13 AM Palmer Dabbelt <pal...@rivosinc.com> wrote: > > > > On Tue, 16 May 2023 19:07:01 PDT (-0700), juzhe.zh...@rivai.ai wrote: > > > Oh, I see. Kito has add /* { dg-do run { target { riscv_vector } } } */ > > > But not all RVV tests has use this and I not sure whether it can work. > > > I think Kito can answer it. > > > If yes, I think we should add all of them. > > > > Unless I'm missing something, it looks like that only checks if GCC is > > compiling for V. Nothing appears to be checking if the system the tests > > are running on supports V. > > > > # Return 1 if the target has RISC-V vector extension, 0 otherwise. > > # Cache the result. > > > > proc check_effective_target_riscv_vector { } { > > # Check that we are compiling for v by checking the __riscv_v marco. > > return [check_no_compiler_messages riscv_vector assembly { > > #if !defined(__riscv_v) > > #error "__riscv_v not defined!" > > #endif > > }] > > } > > > > Those are really just two different things. > > > > It seems pretty reasonably to me to just avoid running the tests when > > the DUT lacks V, but I'm never great with DG. We should probably add > > similar checks for the other ISA extensions, there's going to be a bunch > > of this. > > > > > > > > Thanks. > > > > > > > > > juzhe.zh...@rivai.ai > > > > > > From: Andrew Pinski > > > Date: 2023-05-17 10:02 > > > To: juzhe.zh...@rivai.ai > > > CC: gcc-patches; palmer; Kito.cheng > > > Subject: Re: RISC-V Test Errors and Failures > > > On Tue, May 16, 2023 at 6:58 PM juzhe.zh...@rivai.ai > > > <juzhe.zh...@rivai.ai> wrote: > > >> > > >> Hi, Palmer. > > >> I saw your patch showed there are a lot of run time fail (execution > > >> fail) of C++. > > >> bug-*.C > > >> > > >> These tests are RVV api intrinsics tests coming from Kito's that I have > > >> already fixed all of them. > > >> I just double checked again they all passed. > > >> I think it may be your regression environment does not set up simulator > > >> (QEMU or SPIKE or GEM5) correctly. > > >> For example, did not enable vector extension in simulator, I don't you > > >> may try. > > > > > > So on x86_64, we test to see if you have the right vector unit before > > > running those tests? The same thing was true on powerpc (and I think > > > aarch64 does the same for SVE now too). The reason why I am asking is > > > that I would need to run the testsuite using the simulator as setup > > > for the RISCV ISA I am using rather than the one with everything on. > > > So does the RVV runtime testsuite tests to see if you can run RVV > > > before running them (or running them and return they passed)? > > > > > > Thanks, > > > Andrew Pinski > > > > > >> > > >> Thanks. > > >> > > >> > > >> juzhe.zh...@rivai.ai > > >