Closed kareefardi closed 1 year ago
Why do you have pins outside the die area? That seems like an error unto itself.
You can control the pin shape and "extend" it outside the die area in OR. It is was useful in the early days of OR. Although, it might be unneeded nowadays, I am not sure there is an error by having a pin partially outside the die area of a macro.
The die area is normally meant to enclose the contents. I would remove that usage and report any problems that arise.
Geometric shapes (such as blockages, pins, and special net routing) can be outside of the die area, to allow proper modeling of pushed down routing from top-level designs into sub blocks. However, routing tracks should still be inside the die area.
According to lefdefref, there is nothing wrong with having pin shapes outside the die area.
Are you modeling pushed down shapes?
No but it doesn't mean that it is wrong for OR to be able to deal with such shapes, especially that it supports creating them.
We are fixing this but I don't feel it is a good methodology. I prefer to change it so that we can't create such shapes but don't want to cause problems for you. Is there some advantage to this method?
I know that we are using it. However, I am not sure if it is really needed. Let me check with the team and get back to you.
Describe the bug
Global router reports the following:
[ERROR GRT-0076] Net io_oeb[18] not properly covered.
. Although, that's a normal pin in the design.Expected Behavior
Global router succeeds.
OpenROAD Environment
OpenLane Environment
To Reproduce
issue_reproducible.tar.gz
Relevant log output
Screenshots
No response
Additional Context
OL is behind OR head, but same error happens in OR head. I noticed that this error doesn't happen when the pins are not extending outside the die area.