[pull] master from verilog-to-routing:master #565
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
github-actions
bot
removed
VPR
libarchfpga
lang-python
scripts
libvtrutil
tests
liblog
labels
…s-update-golden [CI] Updated Weekly Golden Tests
Found a bug with how the centroid location of clusters were calculated. The centroid may be located off device which was causing accesses out of bounds in some cases. To prevent this, I have added clamps that ensure that the atoms' relative positions are always on device.
Cleaned up RRGraph Drawing Code
A recent cleanup I made of the way VTR does its versioning added the "--tags" argument to the git describe command. The hope of this option was that it would enable VTR to point to the v9.0.0 tag instead of the v8.0.0 tag; however, this was not the case. In some cases, it was able to find the v9.0.0 tag; however, since this tag is on another branch, many users are unable to find that tag from git describe. This caused the versioning code to fall back on v9.0.0-candidate which is the last tagged version on the branch. This tag is the branching point of v9.0.0, but we do not want to use this tag since 1) it does not use the correct naming scheme (the "-candidate" causes problems with downstream tools) and 2) this is not a complete tag (i.e. it lacks metadata). I reverted this change, so now git describe should stably point to the last full tagged release of VTR on the master branch (which is v8.0.0). This will at least ensure that the version VTR produces is stable. We prefer a stable versioning system based off v8.0.0 over an unstable versioning system based off v9.0.0.
[Build][Version] Reverted Version Tagging Change
…allback [APPack] Initial Placement Fallback
…anups [RRGraph] Small code clean up according to coding style
…te_v0.55 Upgrading to Yosys v0.55 and Updating Slang
This is the second PR that brings in private tunings for the Triple-AP work into VTR master. These are all the tuning changes to the APPack algorithm. This comes with changes to the max displacement threshold values, improved fall-back logic, and better unrelated clustering logic. Also fixed a small issue in the delay derivative calculation of the analytical solver to explicitly handle boundary conditions of the derivative.
[APPack] Tuned Up APPack Code
While testing the AP flow, it is convenient to only focus on one stage of the flow at a time. It would be nice to have a very simplified version of the stages which we know will always work. I have created a new solver called the "identity" solver which acts as an identity matrix where it just passes the solution from the prior partial legalizer iteration along. This allows me to focus on the partial legalizer without having to worry about the solver as I make more substantial changes while working on new applications of the AP flow.
[AP][Solver] Added The Identity Analytical Solver
The weekly tests were failing due to updates to the AP flow which were recently merged in. Updated the golden results.
…lden-update [CI][Weekly] Updated Failing Golden Results
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 : )