-
Notifications
You must be signed in to change notification settings - Fork 406
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
[ren] Separate INT/FP Rename Instantiations #347
Conversation
/** | ||
* TODO This is a bit nasty, but it's currently necessary to | ||
* split the INT/FP rename pipelines into separate instantiations. | ||
* Won't have to do this anymore with a properly decoupled FP pipeline. |
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.
How do you plan on handling int-to-fp/fp-to-int moves without doing this ugly merge step?
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.
If the FP rename pipeline ends up living behind a queue, fp-to-int could be handled the same as it is now. int-to-fp would need to use some sort of structure to match up fp destinations to the uops coming from the int side.
This boots fedora. |
@@ -104,7 +104,11 @@ class BoomCore(implicit p: Parameters, edge: freechips.rocketchip.tilelink.TLEdg | |||
|
|||
val decode_units = for (w <- 0 until decodeWidth) yield { val d = Module(new DecodeUnit); d } | |||
val dec_brmask_logic = Module(new BranchMaskGenerationLogic(coreWidth)) | |||
val rename_stage = Module(new RenameStage(coreWidth, numIntRenameWakeupPorts, numFpWakeupPorts)) | |||
val rename_stage = Module(new RenameStage(coreWidth, numIntPhysRegs, numIntRenameWakeupPorts, false)) |
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.
Nit, but naming this int_rename_stage
might make more sense,
Although if FP-pipeline becomes more decoupled, this naming is fine,
This needs rebasing for a very simple merge conflict. |
…es based on rtypes.
* Refactor how Configs parameterize the Top and TestHarnesses * Bump sha3, testchipip, icenet, firesim
Type of change: other enhancement
Impact: rtl refactoring
Development Phase: implementation
Release Notes
Describe the INT/FP pipelines as separate instantiations of a module, rather than a single instantiation.