Skip to content

Conversation

@eder-matheus
Copy link
Member

@eder-matheus eder-matheus commented Jan 19, 2026

Partially covers the comments made here: #3536 (comment)

This PR adds the ability to show the runtime of the global_route command. It is only enabled by using the flag -show_runtime. This is off by default for reproducibility purposes (e.g., unit tests that relies on the tool log).

Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a useful feature to report the runtime of the global routing process. The implementation is straightforward and well-integrated with the existing TCL interface and documentation. I have a few suggestions to improve const-correctness and ensure the accuracy of the timing measurements.

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@maliberty
Copy link
Member

As I commented there ORFS is already using log_cmd to report the time. Having an off by default option doesn't seem that useful. @stefanottili is this what you are asking for and it is still relevant?

@stefanottili
Copy link

a) not everybody is using ORFS, sometimes running a P&R flow in "one script, without getting in/out of the tool" is a good thing.
b) considering that drt is very verbose with it's runtime, why not grd ?
What's different between drt and grt with regards to unit tests that rely on log files ?

@eder-matheus
Copy link
Member Author

b) considering that drt is very verbose with it's runtime, why not grd ? What's different between drt and grt with regards to unit tests that rely on log files ?

GRT is less verbose than DRT, so the -verbose guards everything that is logged by the tool. Information such as capacity/usage per layer, final congestion, etc. are used in the unit tests to ensure the tool is not changing its behavior. Adding runtime to this flag would break our unit tests.

@maliberty
Copy link
Member

@eder-matheus we suppress runtime related messages in test/helpers.tcl for unit testing to avoid output differences (they occur elsewhere like drt).

Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

1 similar comment
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

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

Successfully merging this pull request may close these issues.

3 participants