-
Notifications
You must be signed in to change notification settings - Fork 413
Fix fixed clusters issue #2495
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
Fix fixed clusters issue #2495
Conversation
Link to QoR results for Titan benchmarks. They are the same as master. |
|
@vaughnbetz |
Please summarize the relative runtime, cpd, wirelength etc. of the master vs. this fix. |
|
Issue runtime: was a few days, now is less than 5 min so it is fixed. |
@soheilshahrouz : need to resolve a conflict. |
Looks like many seg faults in CI. |
…rea_per_tile for regression_tests/vtr_reg_strong_odin/strong_fix_pins_random
@vaughnbetz |
Description
When a large number of clustered blocks are fixed, placement takes a very long time. This is because for picking a random block, we exhaust all blocks until we find a movable block. If most clustered blocks are fixed, it would take a long time to exhaust fixed blocks by random selection. This PR stores movable blocks in a vtr::vector so that a movable random block can be selected more quickly. It also makes reading the placement file more robust.
Related Issue
Issue 2484
How Has This Been Tested?
Types of changes
Checklist: