Yang Liu
Yang Liu
``` LD_LIBRARY_PATH=$RISCV/lib build/pspike --isa=rv64gcv --varch=vlen:256,elen:64 $(which pk) out/v256x64user/bin/stage1/vaadd.vv-0 ``` Did this command alone run fine on your side? It works for me.
That's strange. `out/v256x64user/bin/stage1/vaadd.vv-0` is not supposed to have this many test cases. The last few lines on my side are: ``` TEST_CASE(2111, t0, 0xffffffffffffc000, ld t0, 0(a0); addi a0, a0,...
Are you sure you're using the latest `main` without any changes?
Then I don't know why, the "patch" stage works fine on my side. Spike with pk is indeed a bit unstable for reasons I don't know, but the errors only...
You need to run `git submodule update --init`.
Closed for long periods of inactivity.
I'm currently busy with other things, but I will add them.
I already added vxrm and vxsat support.
Normally, `vstart` is written by hardware on a trap, which is not straightforward to fit into our test framework. `vstart` can also be written by `csrrw[i]`, which is a usage...
Indeed. Then we have to make `vstart` support optional for arithmetic instructions if we add it to the test. Page 14: > For example, some implementations will never take interrupts...