-
Notifications
You must be signed in to change notification settings - Fork 450
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
Fix for test program compilation failures due to lack of zicsr
extension in -march=rvXX...
#484
Conversation
Note the pylint failure is not your fault, and will be fixed by #483. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give the PR a title that someone can read without knowing github issue numbers by heart?
Change looks fine, but I'm a bit concerned about it not working with older GCC versions. Specifically, OpenOCD automatically runs these tests using https://github.com/riscv/riscv-openocd/blob/riscv/.github/workflows/spike-openocd-tests.yml.
Can you confirm that these new flags are supported by the toolchain referred to on line 10 of that file?
Thanks @timsifive .
Sorry - I thought that it was sufficient to link to the issue.
I'm pretty sure that any post GCC 12 toolchain will support |
zicsr
extension in -march=rvXX...
Hi @timsifive - I can confirm that those tests using the xPack toolchain in question still work fine with this PR's change.
|
Thanks for merging @timsifive. |
Fix for:
zicsr
extension in-march=...
#482Note that this fix means that the tests will probably fail to compile with a pre GCC 12 RISC-V toolchain which predates the separation of the
zicsr
(andzifencei
) extension(s) out from the base integer ISA. But I didn't think that it was worthwhile complicating the script further by trying to cater for older toolchains in the script.