-
Notifications
You must be signed in to change notification settings - Fork 4
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
megaboom: branch predictors as macros #210
Conversation
1d6cd0b
to
d314013
Compare
Signed-off-by: Øyvind Harboe <[email protected]>
77e30b8
to
a316de8
Compare
@maliberty @jeffng-or When I create macros for the branch predictors, the floorplan looks much better: Macros are now in four groups:
I'm using mock-area for branch predictors on one hand, but I have not put any effort to figuring out what size they need to be. I'm thinking the area should now be possible to bring down to something near 1000x1000um. |
a316de8
to
ea54066
Compare
Signed-off-by: Øyvind Harboe <[email protected]>
ea54066
to
f97700f
Compare
@jeffng-or @maliberty While interesting that branch predictors as macros clean up the top level floorplan as much as it does, WNS goes from -2872.979248 to -4737.364746. I'm going to keep the additional code I wrote, but I'm not switching to branch predictors as macros. There's a chance that the WNS stems from the suboptimal Branch Predictor macro and that the branch predictor macro can be significantly improved, but I plan to let that lie. |
@maliberty @jeffng-or 1500x1500 layout, looks neat and clean now that branch predictors are off to the side as macros. Upon closer inspection: I'm not sure that it is such a bad idea to have the branch predictors as macros. It would need some further exploration. Hard to tell without better synthesis(levels of logic should probably be closer to 20 to compete with commerical tools ref. 28nm 1000ps tapeout of BOOM). |
@maliberty @jeffng-or WNS coming or going from branch predictors is -2200, which isn't horrible. Perhaps put both branch predictors into a single macro? There's paths from branch 0 going into branch predictor 1, so they are intertwined in some way.
|
Branch predictor macros visible:
WNS from gui_floorplan:
Stage: cts
Base configuration variables