* Minor tweaks to setup-oss-cad-suite
* Switch espresso installation to composite action
* Switch circt installation to composite action

* Added option to disable deprecation of SFC import using wConf

The YosysHQ Github Action for setting up the OSS CAD Suite is very flaky
in CI so instead we can just wget and untar the suite ourselves. It also
seems prudent to try out composite actions to avoid duplication of
installation steps.

Deprecate Fixed Point and Intervals

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Add a deprecation string that can be used for marking things that are
deprecated due to the MLIR-based FIRRTL Compiler (MFC) migration.  Do
not use this anywhere (yet).

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

[circt] Cleanup CIRCT error behavior

Change all docs to use CIRCT in their mdoc regions.  Everything worked
without issue except for one weird mdoc region in hierarchy.md which I
am not sure how it is even legal.  This mdoc region has been disabled
for now.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Improve the error message that trips if firtool is not found.  Add a new
exception and throw this when execution of the firtool process fails.
This commit tries to narrowly only match on the exact condition that
this failed due to firtool not being installed.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Change the behavior of what happens if firtool returns a non-zero exit
code from printing information to stdout to throwing an exception with
this information in the body.  This is done primarily to ease
interoperability with mdoc.  However, this is generally better
principled than the previous behavior of scattering information in
different mediums.  Add a test of this behavior.

Stop intercepting a file not found error if CIRCT fails to print this to
stdout and wrap this in a StageError.  It is better to just let the file
not found exception through as this already includes all the information
necessary to tell the user what the problem is.  Do not test this
behavior (as it is tedious to test).

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

* Bugfix waiveEach not casting. Add waiveAllAs

* Add implicit type constraints to connectable apis

* Swapped order T =:= S for clearer error messages

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

* Fix BitSet decoder API when errorBit=False

    When errorBit is set to False, the original code will return
    `Unit` which will be `()` in interpolated string.

* Add testcases for both errorBit cases in BitSetSpec

* chisel-circt: pullin src/main/scala changes from 0.8.0
* chisel-circt: pullin src/test/scala changes from 0.8.0
* chisel-circt: bump circt verstion to match what is on 0.8.0

* Switch from deprecated setup-scala to setup-java
* Switch from deprecated set-output to $GITHUB_OUTPUT
* Use $GITHUB_STEP_SUMMARY for reporting

* Remove parenthesized forms of:
`.unary_-()`, `.unary_%()`, `.unary_~()`, `.unary_!()`,
`.orR()`, `.andR()`, `.xorR()`,  `.zext()`, 
`.asBool()`, `.asBools()`, `.asSInt()`, `.asAsyncReset()`,
`.asClock()`, `.isLit()`, `.litOption()`, `.litValue()`,
`.abs()`
* Remove protected `Data.bindingToString`
* Remove `RawModule.getPorts`
* Remove `._applyMacroWithMessage` in assert and assume
* Remove `stop` that accepts non-zero return code
* Remove public `WhenContext` constructor
* Remove parenthesized `WhenContext.active()`
* Remove `blacklistPackages`, `builderName`, and `chiselStackTrace` from `ChiselException`
* Remove `MultiIOModule` (`Module` can have multiple `IOs`)
* Remove `chisel3.getModulePorts`
* Undo deprecation of `Data.flatten` which is package private and useful
* Also remove all internal uses of these removed methods

Co-authored-by: Jack Koenig <koenig@sifive.com>

This allows build tools to warn users about possible binary
incompatibility issues when using dependencies that depend on
mutually incompatible versions of Chisel.

This means dropping Scala 2.12.4 support which is broken in Zinc newer
than 1.6.0. Chisel users of Scala 2.12.4 should upgrade to 2.12.17.

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* add upickle to dependency

* implement SerializableModuleGenerator to serialize a parameterized module

* add simple test

* Add mdoc

Co-authored-by: Jack Koenig <koenig@sifive.com>

Co-authored-by: Jack Koenig <koenig@sifive.com>

* Don't copy _ids to a Seq just to Iterate on them

Saves a copy of a large data structure.

* Only add Data to _ids when the binding is constrained

ConstrainedBinding means that the bound Data is scoped to a module.
Since _ids are used for naming of signals within a module, there is no
reason to add Unconstrained Data to the _ids of the Module they were
constructed during. Unconstrained Data include things like literals and
children of Aggregates (which sort of are constrained to a Module but
only via their parent, they are not directly named by the module).

Includes support for waiving unmatched fields from triggering errors, and mismatched widths from triggering errors. Includes extensive documentation and tests.

Co-authored-by: Megan Wachs <megan@sifive.com>

The namespace disambiguates requests for the same name with _<idx>.
Rather than storing every disambiguated name in the underlying HashMap,
it now only stores the base along with the "next available" index. This
makes the logic for checking if a name is already contained in the
namespace slightly more sophisticated because users can name things in a
way that will collide with disambiguated names from a common substring.

For example, in naming the sequence "foo", "foo", "foo_1", the 2nd "foo"
takes the name "foo_1" so the following "foo_1" gets disambiguated to
"foo_1_1". But since we compressed that original "foo_1" into the same
HashMap entry as just "foo", we have to do a form of "prefix checking"
whenever naming something that ends in "_<idx>".

In practice, the saved memory allocations more than make up for the more
complicated logic to disambiguate names because the common case is still
fast.

It used to be implemented with recursion, now it's implemented with a
stack safe reverse and foldLeft.

Also there were no tests for PriorityMux so I added one which helps
prove the change is functionally correct.

* Use SourceInfo in Builder error messages when available

* Use line break instead of semicolon

Co-authored-by: Jack Koenig <jack.koenig3@gmail.com>

Co-authored-by: Jack Koenig <jack.koenig3@gmail.com>