forked from verilog-to-routing/vtr-verilog-to-routing
-
Notifications
You must be signed in to change notification settings - Fork 12
[pull] master from verilog-to-routing:master #565
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
Open
pull
wants to merge
10,000
commits into
SymbiFlow:master
Choose a base branch
from
verilog-to-routing:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
…unts into a local/static helper function
Being based off the packer, APPack also uses iterative re-packing when a dense enough clustering cannot be found. APPack has some special options that it can use to increase the density of clustering further without hurting quality as much as the default flow. Updated the iterative re-packing algorithm to use these options if needed. Having this safer fall-back has allowed me to tune some numbers that I knew would improve the quality of most circuits but was causing a few circuits to fail packing. These few that were failing should now hit this fall-back paths which resolves this issue.
I expect the sanitized test to be the tall pole for the speed of the CI due to its long run time on the testcases. After investigating with Vaughn, we realized that this test was using the debug build of VTR. This was likely making it much slower than it needed to be. To improve the speed of this test, moved it to use the release build. We still want symbols to give good error messages.
…packing [APPack] Iterative Re-Packing
Add CHANZ type
The compatibility CI builds are taking longer than expected, especially for the GCC builds. They appear to be having issues with CCache. Trying to clean up the tests to speed them up. Removed the GCC-11 compatibility test since it was already being tested in the Jammy compatibility test. Removed Odin from the compatibility test since it is not the default flow. Cleaned up some enviornment variables. I found that using a release build caches much better than a debug build. This ends up saving way more time than we gain from using a debug build.
Stage reporting update
…anup [CI] Moved Sanitized Test from Debug to RelWithDebInfo
Flat Routing Visualization
…ng_cost Fix divison by zero when the timing cost is zero
[Build] Updated VTR Versioning
…t-builds [CI] Speeding Up Compatibility Builds
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )