Clean up confusing rr-node lookup convention for x/y location of CHANX nodes #3042
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
…and load_block_rr_indices()
github-actions
bot
added
VPR
soheilshahrouz
changed the title
|
Radom failure due to a known issue #3029 |
vaughnbetz
approved these changes
May 16, 2025
There was a problem hiding this comment.
Thanks @soheilshahrouz . A nice clean up -- the code looks good!
This was referenced May 16, 2025
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.
RRSpatialLookupswaps the x and y coordinates of CHANX wires when putting them in therr_node_lookupdata structure, andfind_node()function swaps them as well. This PR gets rid of these swaps.Addresses #355 and #2978