-
Notifications
You must be signed in to change notification settings - Fork 449
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
Failing debug test case "spike32.SimpleV13Test" #287
Comments
Further information - This test
Jan |
As a side note, another 180 tests fail (exception) due to the recent deprecation of "-rtos riscv" option in OpenOCD (riscv-collab/riscv-openocd#499). |
This is now required to use `-rtos riscv`. Addresses the aside mentioned in #287.
It used to work. I guess something changed in spike's vector implementation, which may have been because the vector spec changed. I'll do some digging. |
This broke in spike commit 308b6db54946d853b47cb5085a06e90aae14145c, which is mercifully short. |
This patch fixes it in OpenOCD. I need to figure out if it's important for OpenOCD to support 0.9 before I just merge that:
|
Thanks, Tim. After applying the two changes above ("enable_rtos_riscv" + the OpenOCD patch), all tests pass for me: $ cd debug
$ make all 2>&1 | tee results.txt
$ cat results.txt | grep "tests returned" | sort | uniq -c
56 1 tests returned not_applicable
384 1 tests returned pass
|
This is now required to use `-rtos riscv`. Addresses the aside mentioned in #287.
This debug test is failing on my machine: "spike32.SimpleV13Test":
cd debug make run.spike32.SimpleV13Test
I am attaching my log: 20200805-104914-spike32-SimpleV13Test.log
Have you please seen this issue already or does it look like a problem in my setup?
After further digging, it turns out that the test always fails when reading back the value of
$v13.b[2]
field (https://github.com/riscv/riscv-tests/blob/master/debug/gdbserver.py#L129). Reading the preceding fields$v13.b[0]
and$v13.b[1]
never failed. Dump of the whole register v13 prior to testing the individual fields (https://github.com/riscv/riscv-tests/blob/master/debug/gdbserver.py#L127) shows that the values are already different than what was written to them. See also the log file.I am running the tests on a Debian 9 machine.
These are the software components I am using (built from source, all should be the latest commits as of now):
Thank you,
Jan
The text was updated successfully, but these errors were encountered: