Skip to content
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

[c.]ebreak tests imply that hardware triggers are implemented #579

Open
marcfedorow opened this issue Dec 17, 2024 · 1 comment
Open

[c.]ebreak tests imply that hardware triggers are implemented #579

marcfedorow opened this issue Dec 17, 2024 · 1 comment

Comments

@marcfedorow
Copy link
Contributor

[c.]ebreak tests fail if there are no hardware triggers supported by hardware.
Hardware triggers are optional though.

@allenjbaum
Copy link
Collaborator

Could you please elaborate on what you mean by "failure"?

The cebreak test simply executes a single c.ebreak, and is expected to trap with the correct epc, tval, and cause CSR values, and return. If it matches what sail does under the same circumstances, it is a success.
Hardware triggers are not involved (that would be a trigger test)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants