-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to check resultdata #57
Comments
The final assembly is in stage2, not stage1. |
Can you try XLEN=64 to see if it's working? Maybe something is wrong under XLEN=32? |
Maybe something is wrong with your setup, check how we did this in the CI, refer to https://github.com/chipsalliance/riscv-vector-tests/blob/main/.github/workflows/build-and-test.yml. |
Thanks,I will try |
Oh, about the magic .word, check the "How it works" section in README. We modified spike to add a "magic" instruction which generates reference result checking code, and then merged back to the original assembly file. |
I run |
It seems XLEN=32 was not well tested in some cases, I'll check later. |
Case: out/v128x32machine/tests/stage1/vaadd_vv-0.S
It seems that the final results were not checked and compared.
The text was updated successfully, but these errors were encountered: