ksco
Make for target 'build-patcher-spike' failed
After meeting prerequisites, I execute make -j40. However, I got the error message as follows：
I check the related files and find that the function
cfg_t::cfg is called in pspike/psike.cc with 12 arguments provided:
But the candidate function in my pre-built Spike expects 13 arguments:
It seems that the call for
cfg_t::cfg in pspike/psike.cc missing the const char * default_priv argument. Could you please help me solve the problem?
We're using some unstable API, so it changes from time to time, please check build-and-test.yml file to use a specific version of spike.
We're using some unstable API, so it changes from time to time, please check build-and-test.yml file to use a specific version of spike.
Thanks, it works.
However, When I change the mode to ‘user’, I get stuck in the tests_patch step, such as
LD_LIBRARY_PATH=/riscv_toolchains/lib build/pspike --isa=rv64gcv --varch=vlen:256,elen:64 /riscv_toolchains/riscv64-unknown-elf/bin/pk out/v256x64user/bin/stage1/vaadd.vv-0 > out/v256x64user/patches/stage2/vaadd.vv-0.patch
I get the error message:
*** FAILED *** (tohost = -1073707433)
*** FAILED *** (tohost = -1073707433)
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.
LD_LIBRARY_PATH=$RISCV/lib build/pspike --isa=rv64gcv --varch=vlen:256,elen:64 $(which pk) out/v256x64user/bin/stage1/vaadd.vv-0Did this command alone run fine on your side? It works for me.
No, the result is failed.
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, 8)
TEST_CASE(2112, t0, 0xa989e5f32751c914, ld t0, 0(a0); addi a0, a0, 8)
TEST_CASE(2113, t0, 0xffffffffbfffc000, ld t0, 0(a0); addi a0, a0, 8)
---
Are you sure you're using the latest
mainwithout any changes?
Yes, it's up to date with the latest main without any changes. And I see that the third argument of most of the test cases is 0x0, only a few are non-zero.
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 happen at the later "merger" stage on my side, retrying a few times will get a successful build.
After I git clone the repo to my local, I find that there are no files in env/riscv-test-env. So I excute git clone https://github.com/riscv/riscv-test-env.git in env/. Is it the possible reason for the error?