-
Notifications
You must be signed in to change notification settings - Fork 262
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
global route: add policy on iteration reporting on hard runs #1333
Merged
maliberty
merged 3 commits into
The-OpenROAD-Project:master
from
Pinata-Consulting:global-route-reporting-policy
Aug 13, 2023
Merged
global route: add policy on iteration reporting on hard runs #1333
maliberty
merged 3 commits into
The-OpenROAD-Project:master
from
Pinata-Consulting:global-route-reporting-policy
Aug 13, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The default behavior if the user didn't specify GLOBAL_ROUTE_ARGS is to first make an attempt with a few iterations, if this is a hard global route, start from scratch, try harder and logging. The goal here is to make ORFS handle the simple cases without fuzz and to make the harder cases more easily debuggable without having to go spelunking in Tcl. If GLOBAL_ROUTE_ARGS is specified, then we do only what the GLOBAL_ROUTE_ARGS specifies. Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
Example with sky130hd/microwatt. First, comment out the GLOBAL_ROUTE_ARGS, so that we enable the policy we want to test:
Then we get:
The reports are irrelevant in size compared to the .odb files:
Examine reports in GUI after, e.g. 5 iterations:
Now we can load congestion report 21 and zoom in on the problems: |
fix tcl gaffes Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
maliberty
reviewed
Aug 9, 2023
Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
maliberty
reviewed
Aug 12, 2023
maliberty
approved these changes
Aug 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default behavior if the user didn't specify GLOBAL_ROUTE_ARGS is to first make an attempt with a few iterations, if this is a hard global route, start from scratch, try harder and logging. The goal here is to make ORFS handle the simple cases without fuzz and to make the harder cases more easily debuggable without having to go spelunking in Tcl.
If GLOBAL_ROUTE_ARGS is specified, then we do only what the GLOBAL_ROUTE_ARGS specifies.