Mixing in these traits enables overriding the implicit clock or reset
from within a Module.

They were private and [deprecated] protected methods used by an already
removed API for setting the clock and reset of a Module from the
outside.

When creating large numbers of Definitions, copying the
globalNamespace back and forth becomes a performance bottleneck.

Now it will fetch llvm-firtool with classifier for the current system
rather than the full artifact which contains binaries for all platforms.

Legacy `--print-ir-after-all` has been replaced by this new argument.

* Use Java 17 to build documentation in CI

This avoids CI flakiness due to scala-cli needing to download Java 17 at
runtime and timing out.

* Exclude docs project from Unidoc

The docs project includes logic only used for generating mdoc, it should
not be included in the generated ScalaDoc as it is not actually included
in the published Chisel artifacts.

This also helps avoid flaky CI issues--the publish step will no longer
compile the docs subproject. Compiling the docs subproject requires
scala-cli which requires Java 17. Downloading Java 17 at build time can
timeout, causing flaky CI. Note that the publish step uses Java 8 so
that we can guarantee the published artifacts work on Java 8.

fix up path issue in build.sc

Whereas in the past, the user was expected to provide the firtool binary
on the PATH, Chisel will now manage the firtool binary automatically.
Chisel users the following 3-step process for determining which binary
to use:

1. If environment variable FIRTOOL_PATH is set, it will check for
   firtool in that directory
2. It will check the classpath for firtool provided by
   chipsalliance/llvm-firtool
3. It will download a default version of chipsalliance/llvm-firtool

Both (2) and (3) will store the firtool binary in a sensible location
depending on the user's operating system. See dirs-dev/directories-jvm
for more information. The user can override this location by setting the
FIRTOOL_CACHE environment variable.

* [docs] Fix release ordering
   Ensure that 6.0.0 > 6.0.0-RC1 > 6.0.0-M3
* [docs] Release candidates count for latest

Go all in on leaf marking for don't touched values. This preserves current behavior. As options expand, the API can change then.

Go all in on leaf marking for don't touched values.  This preserves current behavior.  As options expand, the API can change then.

Add an argument to dontTouch which allows placing don't touch annotations on the leaves of aggregates. Default this option. This results in the same behavior as what the current dontTouch effectively does today. Don't touch of an aggregate is on it's plain meaning different from don't touch on the leaves of an aggregate. Making the annotation a bit more precise allows greater freedom in code generation and allows catching contradictory requests by the programmer.

* [binder] Update API `FIRRTLDirection` for CIRCT 1.60.0
* [binder] Remove dedup option (#3641)
* [ci] bump circt/update-staging-branch to 1.2.0
* [cd] Bump CIRCT from firtool-1.59.0 to firtool-1.60.0
* [binder] Update firtool-lib C-API to allow the creation of multiple options
* [binder] Remove firtool-1.61.0 features
* [circt] Use new public-modules option

This is an automated commit generated by the `circt/update-circt` GitHub
Action.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Co-authored-by: Sprite <SpriteOvO@gmail.com>
Co-authored-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Co-authored-by: chiselbot <chiselbot@users.noreply.github.com>

This is the right place in the Chisel type hierarchy for Property as
it exists today. Property types can be used in Aggregates, and are not
themselves Aggregates in their current form. Making Property extend
Element allows much of Chisel's internal reflection to work as
expected when Property types are used in Aggregates.

Add a `dontTouchLeaves` which places don't touch annotations on the leaves of aggregates.  This does what the current `dontTouch` effectively does, but is explicit.

A dead import dies.

Fix spelling error

This should enable them to be indexed and thus searchable as part of the
website (both by Algolia and by Google).