Provide direct conversion from ChiselIR to FIRRTL.
Provide Driver support for dumping ProtoBuf.

Resolves #841

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

Documentation for example had parameters in wrong order, and was missing @param. Additionally, it was lacking a module wrapper. This has been corrected.

Add chisel3.experimental.IO for programmatic port creation in Raw and
MultiIOModules. suggestName is required to name ports that cannot be
named by reflection. Two ports cannot be given the same name.

Fixes #763
Add tests for #763 and #472

This has a few implications
* Constructing a literal no longer increments _T_ suffixes
* Internally, wrapping a literal Bits in Node(...) will work
* Literal Bools work in withReset/withClockAndReset

The Vec constructor invokes the gen argument for each element in the
Vec. Since VecInit invokes cloneSupertype which touches every element of
the input Seq, this was an n^2 operation. Vec.apply accepts its
arguments by value so cloneSupertype is only called once. It then calls
cloneType on that once for each element in the Vec, which is constant
time reducing the overall complexity of VecInit to just n.

* Add test for UIntToOH

* Pad UIntToOH inputs to support oversized output widthds

* Optimize Bits.pad in case of known widths

* Add missing import and fix test in OneHotMuxSpec

They should only be instantiated through their companion objects.

Resolves #815

Resolves #809

If autoclonetype is unable to determine an outer class, this attempts to insert a null (and give a deprecation warning), preserving old behavior (in some cases) where the new behavior doesn't work.

This doesn't provide full compatibility with old autoclonetype: this does not attempt null insertion in the general first argument (if it's not an outer class reference). Reasoning is that inserting a null for an explicit argument is probably not the right thing to do, and will likely cause a difficult-to-debug NullPointerException (whereas that would be unlikely for an outer class, which is not always referenced in Bundle subclass code).

PiperOrigin-RevId: 187258707

SyncReadMem.read with an enable signal currently only works in
compatibility mode, where Wires are implicitly initialized to
DontCare.  Fix by explicitly assigning DontCare to the Wire.

This might fix #775.

Makes Builder.updateBundleStack a bit stricter in deciding how many stack frames to discard by additionally matching against method names and deleting stack frames at or above the frame currently being inserted.

* Generalize ChiselAnnotation

This allows us to delay creation of Annotations till elaboration is
complete. Also update all annotation-related code.

* Add RunFirrtlTransform

Use a Chisel-specific RunFirrtlTransform API to preserve behavior of old
ChiselAnnotation (now called ChiselLegacyAnnotation)

* Use unique test directories in ChiselRunners.compile

Add companion objects to macro classes

Workaround for unconditional invalidation of macro classes in
incremental recompilation

* Remove checkboxes from issue/pr templates.

* Compact template text and try to make meta information comments.

* Respond to comments - remove bullet point usage.

Revert "Aggregate coverage - discover a working combination of aggregate usage to enable coverage of subprojects. (#782)" (#786)

This is still broken - it publishes multiple jars.
This reverts commit e08da912.

Aggregate coverage - discover a working combination of aggregate usage to enable coverage of subprojects. (#782)

* Generate aggregate coverage but publish a single Jar

* Reduce the aggressive dis-aggregation as it breaks super project aggregation.

* trying to get aggregate coverage working again ...

* Use the right incantation to enable aggregation for only the coverageReport task.

It appears #754 breaks more code than I thought, so this makes it a soft error (with a runtime deprecation warning - to get people to fix their stuff before we break it for real) for now.

This additionally changes the autoclonetype errors to be more deterministic (reporting class names instead of object names) in the most common cases, to allow the deprecations manager to deduplicate warnings.

Changes the API such that IO(...) clones. All Bundles will need to be clone-able, but auto clone type is expected to handle most cases.

* Better support for autoclonetype of nested Bundles

* Move bundleStack to dynamicContext

* prefer $outer if available, make guesses distinct

* Catch IllegalAccessException in autoclonetype
In strange circumstances this type of exception can occur when accessing $outer

BuildInfo.BuildTime appears to cause sbt to always recompile BuildInfo to get
the latest time, which causes a recompile on any package that depends on
chisel3. This is quite painful for doing development on any Chisel projects.
BuildTime doesn't actually appear to be in use, and removing it fixes the
unnecessary recompilation issue.

Add runtime warnings for use of deprecated Chisel methods. This is done using a macro that takes the message from a `@deprecated` annotation, and adds a call to `Builder.deprecated`.

Reasoning is that by default, Scala doesn't print all deprecations, and that it's somewhat tricky to notice them - yet some support questions revolve around the use of deprecated and terribad API. This now prints warnings for uses of deprecated functions at runtime, and aggregates them by error and line to avoid spam. Also included is convenient information on enabling scalac deprecations.

This also changes how line numbers for Chisel's error facility is determined, using prefix string comparison of the stack trace element classnames, instead of checking if the class is a subtype of UserModule. The previous one (specifically, calls to Class.forName) seems to interact badly with reflection-based cloneType when called at scale. This should also give more accurate reporting of errors that are in user code but outside of a UserModule.

It turns out that `@deprecated` on macro functions don't do anything, so this changes the tags to the functions that the macros point to, which seems to work properly. It also turns out that there's a bunch of uses of deprecated functions in chiselTests which needs to be fixed.

Not all `@deprecated` functions are also annotated with `@chiselRuntimeDeprecation`, because they're still used in Chisel internals, and we can't track whether they're called by the user or by Chisel and it will give a misleading error. These are a small amount of functions.

Auto clone type 🦆