-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bump Spike to latest commit #1507
Comments
Perhaps not? When I do so I get this... Before bumping Spike:
After bumping Spike:
|
I thought that this might work and perform the tests on the two
But it didn't and I got this:
|
When bumping Spike, I built two newlib toolchains ( Steps:
I then just copied the two results into one test result block in the commit message. |
Ah - thanks a lot for clarifying @cmuellner. |
Addressed by this PR: |
I'd like to prepare a PR to bump Spike from riscv-software-src/riscv-isa-sim@20a2b6d to the latest commit riscv-software-src/riscv-isa-sim@f7d0dba.
One of the reasons being this:
targets/RISC-V/spike32.py
tests failing riscv-openocd#1098 (comment)I bumped Spike locally in preparation for creating a PR but I am not clear on how to sanity check that the change is safe.
I have run the test suite for the bare-metal/Newlib toolchain and the results before and after this change are identical:
However I'm not clear on how to run the test suite to get results similar to those in the previous "bump Spike" PR which has results for a different set of
arch/abi
combinations:And I'm not sure if I should also be running the
make report-linux
tests?Can anybody give me some guidance on this please?
Thanks.
The text was updated successfully, but these errors were encountered: