RISCV: integrate translator fixes for Renode reports #958-#962 - #44
Open
carlosqwqqwq wants to merge 5 commits into
Open
RISCV: integrate translator fixes for Renode reports #958-#962#44carlosqwqqwq wants to merge 5 commits into
carlosqwqqwq wants to merge 5 commits into
Conversation
added 5 commits
September 7, 2026 14:16
This was referenced Sep 7, 2026
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
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.
Summary This integration branch combines the five focused RISC-V translator fixes already proposed in #36, #37, #38, #39, and #40. The corresponding Renode reports are #958, #959, #960, #961, and #962. ## Included fixes - canonicalize malformed half operands before
fclass.h; - accept dual-owner Zbb/Zbkb instructions when either owner is enabled; - enforce the additional prerequisites of Zcb instructions; - gate scalar M instructions onM; - remove the obsoleteSFENCE.VMdecode branch. Each change remains a separate commit with the original issue-numbered message. This branch exists to let the infrastructure and Renode integration tests exercise the complete dependency update in one CI-visible revision. ## Validation The public reproduction suite is available at https://github.com/carlosqwqqwq/renode-issue-reproduction-template. The Renode integration PR will register the same five cases as Robot tests.Downstream integration
The matching infrastructure pointer is proposed in renode-infrastructure #245, and the top-level Robot regression is proposed in Renode #989.
Reproduction revision
The public baseline run is pinned to Renode commit
f1dd1b4af7838b45a925c17603cdfed0a583844ain the workflow. Verification run: https://github.com/carlosqwqqwq/renode-issue-reproduction-template/actions/runs/34097905145