FIXES ISSUE #827: Improve Zclsd Constraint Visibility Outside of operation() Function #907
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this PR resolves issue #827 by moving the
Zclsd
constraint from theoperation()
function to the instruction-leveldefinedBy
field inc.ld.yaml
, improving visibility for downstream tools such as disassemblers that do not evaluateoperation()
logicwhy not used the suggested schema format?
This format is not valid under the current
inst_schema.json
constraints. Specifically,definedBy
only supportsstring
,anyOf
,allOf
,oneOf
, ornot
constructs based onrequires_entry
, and does not allow architecture-specific keys likeRV32
orRV64
So this approach had to be adapted within the allowed schema