-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new decoder #3498
base: dev
Are you sure you want to change the base?
The new decoder #3498
Conversation
We are still on the way to upgrading to Chisel 5. Thank you for cc me. We will bump rocket first to the version before new decoder table and then bump to the latest with changes on the decoder table. Btw, we still have some local commits in Openxiangshan/rocket-chip. I'll see whether they should/could be upstreamed to chipsalliance. I agree it would be better to follow upstream rocket. |
e5d136b
to
71a0824
Compare
Spot my bug in chipsalliance/chisel#2924 |
ee9d52d
to
1ff5e30
Compare
Assign the Zb/Zk to @cyyself, I'll skip them in this PR by mask them off. After Chisel merging chipsalliance/chisel#3563 I'll bump Chisel version to 3.6.1 and 5.0.x and get this PR merged, CI for this PR is based on my hotfix branch in Chisel. |
4599f46
to
168524d
Compare
TODO: need - release version of chisel 3.6.1, 5.1 - Zb/Zbk support - riscv-opcode path configurable
168524d
to
a5d9d5a
Compare
Original
IDecode.scala
is really hard to maintain which use the view from each instruction rather than each control field.This PR remove original decoder with new [DecodeTable] in Chisel.
It will be a non-small refactor, but it can help us adding new instructions and have a better understand to the uarch.
After this PR is landed, all original IDecode will be moved into an "legacy" folder, downstream user can still use them if they wish, but after Boom and Xiangshan migrated, they will be removed. cc @jerryz123 , @poemonsense
sequncer/rvdecoderdb will be upstreamed to chipsalliance as a part of RC after all test clean.
BTW, I found the Zb/Zk UOP was really a bad design...
Type of change: other enhancement
Impact: API addition (no impact on existing code)
Development Phase: proposal | implementation
Release Notes
Switch to DecodeTable API.