riscv: accept dual-owner bitmanip instructions with either extension - #37
Open
carlosqwqqwq wants to merge 1 commit into
Open
riscv: accept dual-owner bitmanip instructions with either extension#37carlosqwqqwq wants to merge 1 commit into
carlosqwqqwq wants to merge 1 commit into
Conversation
This was referenced Sep 7, 2026
carlosqwqqwq
force-pushed
the
959-zbkb-dual-owner-gate
branch
from
September 7, 2026 16:19
dce3e6d to
a003c4b
Compare
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
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
The first
ensure_additional_extension(ZBB)call raises the illegal-instruction exception before the Zbkb alternative is tested. Use a non-raising any-extension check for the dual-owner instruction family, preserving the illegal-instruction path when neither extension is enabled.Validation
Fixes renode/renode#959
Public reproduction and integration
The corresponding public Robot reproduction is available at
https://github.com/carlosqwqqwq/renode-issue-reproduction-template/tree/main.
The focused change is also included in the combined integration branch in
tlib #44, followed by
renode-infrastructure #245
and Renode #989.