Migrate to RISC-V Compatibility Framework (RISCOF) #108
Conversation
This file contains 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
jserv
reviewed
Jan 27, 2023
jserv
reviewed
Jan 27, 2023
mk/riscv-arch-test.mk
Outdated
| endif | ||
| $(Q)$(MAKE) --quiet -C $(ARCH_TEST_DIR) clean | ||
| $(Q)$(MAKE) --quiet -C $(ARCH_TEST_DIR) | ||
| $(Q) python3 -B $(RISCV_TARGET)/setup.py --riscv_device=$(RISCV_DEVICE) |
There was a problem hiding this comment.
There is no space between $(Q) and python3. That is, $(Q)python3.
jserv
reviewed
Jan 27, 2023
jserv
reviewed
Jan 27, 2023
jserv
reviewed
Jan 27, 2023
jserv
reviewed
Jan 27, 2023
jserv
reviewed
Jan 27, 2023
jserv
reviewed
Feb 6, 2023
jserv
reviewed
Feb 6, 2023
This commit updates the version of riscv-arch-test and introduces the RISC-V Architectural Test Framework (RISCOF) into emulator. In riscv-arch-test part, the following shows the old and revised version. - Old: branch old-framework-2.x - New: branch main and commit 933dddd In RISCOF part, it uses config.ini to configure the plugins to be used — the device-under-test (DUT) and the reference model (REF). The ISA specification defines the available ISA extensions in emulator and users can modify via YAML file in DUT's folder. Besides, the file setup.py generates the config.ini automatically and modifies the ISA specification based on user's input. - DUT: rv32emu - REF: sail_cSim In the other hand, RISCOF uses riscv-gnu-toolchain to compile the tests in riscv-arch-test. Therefore, change the toolchain from riscv-none-elf-gcc-xpack to riscv-gnu-toolchain in Continuous Integration (CI). Finally, summarize the test report based on the latest revision of rv32emu. - Passed ISA in riscv-arch-test: I, M, C, Zicsr (privilege), Zifencei Close sysprog21#49
|
Thank @Risheng1128 for the great work! |
vestata
pushed a commit
to vestata/rv32emu
that referenced
this pull request
Jan 24, 2025
Migrate to RISC-V Compatibility Framework (RISCOF)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit updates the version of riscv-arch-test and introduces the RISC-V Architectural Test Framework (RISCOF) into emulator.
In riscv-arch-test part, the following shows the old and revised version.
In RISCOF part, it uses config.ini to configure the plugins to be used — the device-under-test (DUT) and the reference model (REF). The ISA specification defines the available ISA extensions in emulator and users can modify via YAML file in DUT's folder. The file setup.py generates the config.ini automatically and modifies the ISA specification based on user's input.