[JSON]: Handling Optional Operands #17
Conversation
snapdgn
changed the title
operands
|
[WIP]: This needs more work. The logic for extracting operands is not sound currently, as we need to extract it from the actual |
|
This currently extends the operands with an optional boolean field: |
|
Sorry about the recent commits. I was working on this issue and accidentally committed here. I've since reverted the changes. |
|
Let me know if you have any further feedback/suggestion. If this looks good, should i go ahead and squash the commits, with a proper descriptive message? |
No further comments. I was going to squash and merge, but you would be able to create your preferred commit if you squash. Thanks! |
This commit enhances the JSON Backend to properly handle instructions with optional operands.
Previously, these operands were not handled correctly.
The implementation introduces two new fields:
`optional`, which indicates whether an operand is optional (boolean),
and `default`, which holds the default value if no value is specified.
for 'vle16.v':
Before:
```
{
"operands": [
...
{ "name": "vm", "type": "bits(1)" }
...
]
}
```
After:
```
{
"operands": [
...
{ "name": "vm", "type": "bits(1)", "optional": true, "default": "v0.t" }
...
]
}
```
Fixes: ThinkOpenly#2
|
Squashed the commits.Let me know if you'd like any modifications to the commit message. Otherwise, I think we're ready to proceed with the merge. |
No description provided.