-
Notifications
You must be signed in to change notification settings - Fork 727
Gpl: remove filler removal cap #8480
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
Gpl: remove filler removal cap #8480
Conversation
Signed-off-by: LucasYuki <[email protected]>
Signed-off-by: LucasYuki <[email protected]>
Signed-off-by: LucasYuki <[email protected]>
Signed-off-by: LucasYuki <[email protected]>
|
clang-tidy review says "All clean, LGTM! 👍" |
|
I'm confused as the issue says but this is |
|
As mentioned on a previous meeting we noticed it could be beneficial to remove the max cap filler removal, and allow for all fillers to be potentially removed. Initially we wanted to remove at most 10% of the fillers. Although, there was a bug which we were accidentally removing all fillers, but even still this showed as a good outcome on some private designs, since after fixing the bug and removing only 10% of fillers showed congestion problems during GRT on private designs. By removing the max cap we see no divergences during GPL (on contrary to what I observed previously where multiple public designs were diverging consistently). So we understand it would be better to instead of fixing the cap, just remove it. Since we do not see divergences and private designs benefit from removing the cap. |
|
Needs a small metric update |
|
clang-tidy review says "All clean, LGTM! 👍" |
Signed-off-by: LucasYuki <[email protected]>
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
All green @maliberty |

Issue #8477.
Removes the 10% limit of fillers cells removed during routability.