Update VTR 9 branch with faster check_non_configurable_edges #2874
Conversation
This file contains hidden or 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
github-actions
bot
added
VPR
|
The checks that are not passing will never complete since they are only on the Master branch. @vaughnbetz Who should merge this? |
|
Thanks for the reminder; merging. |
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.
We previously checked every node in a route tree against all non-configurable RR sets, leading to O(n²) complexity. This PR limits checks to RR sets within the route tree, reducing complexity to O(n). As a result, the check_all_non_configurable_edges() function's execution time dropped from 2045s to 1.1s on the bgm benchmark in a 7-series architecture.