> FYI. I have the some failures as juzhe mentioned, with the emulator > qemu version qemu-riscv64 version 8.1.93 (v8.2.0-rc3). The entire log > may look like below: > > Executing on host: > /home/box/panli/riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc/xgcc > -B/home/box/panli/riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc/ > /home/box/panli/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/builtin/strcmp-run.c > -march=rv64gcv -mabi=lp64d -mcmodel=medlow --param=riscv-autovec-lmul=m1 > --param=riscv-autovec-preference=fixed-vlmax -fdiagnostics-plain-output > -ftree-vectorize -O3 --param riscv-autovec-lmul=m1 -O3 -minline-strcmp > -lm -o ./strcmp-run.exe (timeout = 600) > > spawn -ignore SIGHUP > /home/box/panli/riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc/xgcc > -B/home/box/panli/riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc/ > /home/box/panli/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/builtin/strcmp-run.c > -march=rv64gcv -mabi=lp64d -mcmodel=medlow --param=riscv-autovec-lmul=m1 > --param=riscv-autovec-preference=fixed-vlmax -fdiagnostics-plain-output > -ftree-vectorize -O3 --param riscv-autovec-lmul=m1 -O3 -minline-strcmp -lm -o > ./strcmp-run.exe^M
Thanks, it must be a bug if you both see it. But I cannot reproduce it yet for some reason. I tried your exact parameters (just didn't use newlib). Also, for Juzhe it seemed to fail without -minline-strcmp for you it fails with it. Maybe my testcase uses undefined behavior? Could you try reducing SZ to 1 for a test? Regards Robin
