Skip to content
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

Document the difference between "DFFRAM Compiler" and "DFFRAM/OpenLane" #171

Open
xobs opened this issue Nov 26, 2022 · 1 comment
Open

Comments

@xobs
Copy link

xobs commented Nov 26, 2022

The README lists DFFRAM densities for both "DFFRAM Compiler" and "DFFRAM/OpenLane". Please elaborate on what this means, since "DFFRAM Compiler" appears to be 2-3x better than "DFFRAM/OpenLane".

My reading is that if you use the output from DFFRAM in a commercial compiler tool, you can improve it by 3x versus using OpenLane, but I'm not sure if that's what it means.

@antonblanchard
Copy link
Contributor

My understanding:

  • DFFRAM Compiler uses the entire DFFRAM flow where it places all instances
  • DFFRAM/Openlane uses the DFFRAM verilog, but relies on OpenLane (well OpenROAD) to do placement.

It's not a comparison to commercial tools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants