Skip to content

[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
wants to merge 10,000 commits into
base: master
Choose a base branch
from

Conversation

pull[bot]
Copy link

@pull pull bot commented Dec 2, 2020

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

soheilshahrouz and others added 30 commits July 5, 2025 21:00
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.
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.
…anup

[CI] Moved Sanitized Test from Debug to RelWithDebInfo
…ng_cost

Fix divison by zero when the timing cost is zero
…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
Projects
None yet
Development

Successfully merging this pull request may close these issues.