You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pinning artifacts can be useful with OpenROAD flows because some targets can take a very long time to run and hardly ever change:
Netlist of a large register file, multiplier, floating point unit, etc. may hardly ever change, so pin these artifacts and only re-synthesize the parts of the design that is under active development
Macro and pin placement is only known after placement, which can take a long time and also it may be desirable to keep macro placement and pin placement stable while other parts of the design changes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The-OpenROAD-Project/bazel-orfs#367
Pinning of artifacts
Pinning artifacts can be useful with OpenROAD flows because some targets can take a very long time to run and hardly ever change:
MODULE.bazel changes
Create a pinning repository:
BUILD.bazel changes to define pinned artifacts
Using pinned artifacts from a BUILD.bazel file
Updating pinned artifacts
This will build the artifacts, upload them to the bucket and update
artifacts_locked.txtBeta Was this translation helpful? Give feedback.
All reactions