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

Testing & Conformance #78

Open
adurbin-rivos opened this issue Oct 10, 2023 · 1 comment
Open

Testing & Conformance #78

adurbin-rivos opened this issue Oct 10, 2023 · 1 comment

Comments

@adurbin-rivos
Copy link
Collaborator

We have a section about testing & conformance. We should fill it out and indicate the resources available as well as the proper verbiage as it's not 100%. Ken Dockser (@kdockser) indicated he'd help with the wording. Ken, do you have thoughts?

@kdockser
Copy link
Collaborator

Here are some initial thoughts:

  • Normally we use the term "Compatible" in RISC-V when we are performing some checks to see if the implementer understood the spec. We should save Conformance and Compliance for much more rigorous tests that check for a complete match with the specification. If this is a behavioral check, then these more rigorous checks would need to cover all scenarios.
  • If we are using 3rd party tests, we should indicate what part of the BRS spec they cover.
  • We always want to make it clear that these tests are by no means sufficient and it is up to the implementer to verify their implementation is correct and matches all the requirements of the spec.

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