feat(backends): add QEMU generator for RISC-V instruction set #1258
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AnimeshAgarwal28
requested review from
ThinkOpenly and
dhower-qc
as code owners
ThinkOpenly
changed the title
- Implement a generator that generates insn32.decode for qemu. - Move load_full_instructions to generator.py so that other generators can use it. Resolves issue: riscv-software-src#1255
AnimeshAgarwal28
force-pushed
the
feat/qemu-generator
branch
from
e20d6fb to
c212fc6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 generator attempts to generate insn32.decode file in the qemu project. Currently UDB does not have instruction formats so I have added a basic mapping in the python script and a todo to remove it once the UDB has that information.
To generate insn32.decode run the command inside the backends/generators/qemu/ directory:
python3 generate_insn32_decode.py --include-all --arch BOTH --output generated_insn32_decode_output
Resolves issue: #1255