-
Notifications
You must be signed in to change notification settings - Fork 17
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
Single cycle mult #295
Closed
Closed
Single cycle mult #295
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
Need a minimum of 2 (this is what is used in OpenTitan) to enable back to back requests without stall cycles.
Update code from upstream repository https://github.com/lowrisc/cheriot-ibex.git to revision ea2df9db3bcea776f0dc72d6d89c31c73798ecd4 * Feed RV32M through ibexc_top_tracing/ibexc_top (Greg Chadwick) * Switch to no bitmanip by default (Greg Chadwick) * Feed RV32B through in ibexc_top (Greg Chadwick) Signed-off-by: Greg Chadwick <gac@lowrisc.org>
This is effectively a no-op change. Before the latest Ibex was vendored we had no bitmanip (the RV32BFull parameter was not fully passed through) and RV32M was the fast multiplier. Sadly the single cycle multiplier seems to be increasing timing pressure. It does just meet timing but greatly increases synthesis times. As it's implemented with in-built FPGA DSP blocks it shouldn't be a big issue to use it so something to examine here but for now leave things as they are.
For reviewing this is the relevant commit 03d918a |
Converting to draft until SRAM PR is done. |
@@ -734,7 +734,7 @@ module sonata_system | |||
.HeapBase ( tl_main_pkg::ADDR_SPACE_SRAM ), | |||
.TSMapBase ( tl_main_pkg::ADDR_SPACE_REV_TAG ), | |||
.TSMapSize ( RevTagDepth ), | |||
.RV32M ( ibex_pkg::RV32MFast ), | |||
.RV32M ( ibex_pkg::RV32MSingleCycle ), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In principle looks fine to me as long as we can meet timing.
Closing in favour of #314 |
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 sits on top of #279 and shouldn't be merged until that has been merged.
Using v2021.1 enabling the single cycle multiplier works fine, no major change in implementation time and implementation results are good. I'd avoided doing it initially as it wasn't working so well under v2023.1/v2024.1 but as has been discovered those versions don't implement Sonata as well for whatever reason (#289)