You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: