-
Notifications
You must be signed in to change notification settings - Fork 25
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
Proxy pins for implicit verilog pins no longer working #61
Comments
@RTimothyEdwards Is this related to LEF based LVS where there are no underlying cell defintions? On full device level LVS, when I read the spice libraries, this isn't a problem. Maybe adding proxy pins only on black boxes would be a solution. |
Yes, that's what I had in mind. Allowing proxy pins on black box cells---if and only if they come from verilog (which is the only format that allows implicit pins). My original solution was too broad and led to the over-use of proxy pins, which is what your code corrected. But I would still like the proxy pin solution to work in the narrowest case. |
The big problem here is that your last pull request that redid the |
Do the implicit pins show up on gate level verilog that is automatically generated from openlane? |
@d-m-bailey : Yes, it does show up in output from openlane. A good example is from the vezzal repository at https://github.com/lankasaicharan/vezzal , under
The |
Requiring prototypes of all modules is always an option, but I rather liked the simplicity of netgen just handling the implicit pins. |
I believe one of the intermediary commits had the proxy code just commented out rather than removed. |
Possibly related to The-OpenROAD-Project/OpenLane#1380 ? |
Since merging code related to pull request #59, netgen no longer correctly handles implicit pins in verilog. This issue is caused by the fact that verilog syntax allows pins to be missing from a module instance call if those pins do not connect to anything. This case was previously handled by the "proxy pins" method.
The text was updated successfully, but these errors were encountered: