-
Notifications
You must be signed in to change notification settings - Fork 893
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
Add a Han-Carlson option for $lcu
mapping
#4779
Conversation
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.
I left some comments but by me it's fine to merge as is
tests/techmap/kogge-stone.tcl
Outdated
design -load init | ||
chparam -set WIDTH $i | ||
yosys proc | ||
equiv_make -blacklist ppa.nomatch lcu _80_lcu_kogge_stone equiv |
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.
The fact that this matches on internal names makes me think we are using the wrong command to check equivalence here
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.
looks like the folklore is opt_clean
before equiv_make
$lcu
mapping$lcu
mapping
The Han-Carlson parallel-prefix adder (PPA) is an adder construction for ASIC use with an attractive tradeoff. We expect similar delay to Kogge-Stone PPA but better area. I have implemented it in the same procedural style as the current Kogge-Stone and Brent-Kung PPAs. I'm testing it by proving equivalence with
equiv_simple
for bit widths from 1 to 16. I have additionally replaced the test for Kogge-Stone with the same approach. To sweep a variable, full TCL scripting is necessary, which Yosys supports. This PR adds support for using TCL scripts in tests. The HC-PPA and KS-PPA tests take 120ms and 95ms on my Zen 4 machine, respectively.I'm not really sure what to do with the priority integer at the beginning of the module name. Reviewers may test the tests by locally modifying the designs and watching the tests fail