shared build seems to require a specific version of glibc and causes a build failure of downstream tools. This PR adds -static tarball to the artifact.
Give write permissions to jobs that upload release assets.
Set the release-tag explicitly so the upload action knows where to upload on manual runs (on a tag). When triggered by a release this isn't needed but doesn't hurt.
Bump the upload-release-assets action v2 -> v3: https://github.com/AButler/upload-release-assets/releases/tag/v3.0
(This is needed for the release-tag support, also fixes a warning about node version).
Also install the OM linker as part of the minimal firtool installation.
This will be included in both the nightly and published releases.
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Switch from using "clang-12"/"clang++-12" to just "clang"/"clang++". This
doesn't appear to be necessary and will help unify the future use of
GitHub caching.
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
The name of the artifact that include the nightly and published `firtool`
was changed from `firrtl-bin` to `firtool-bin`. This caused a bunch of
other CI to stop getting the latest version (and will break CI on the
1.52.0 release). I'm fine with the name change. I would like to delay
the name change until a later point. This reverts the name change back to
the original.
CC: @SpriteOvO
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Use less resource intensive options for building nightly releases of CIRCT
full. The GitHub runners will run out of disk space if using
"relwithdebinfo" and/or "asserts=on". Use "release" and "asserts=off".
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Jack Koenig