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

Adds a new method, chiselTests.Util.containsCause, that will search
for a polymorphic exception anywhere in a stack trace. This is useful
if exceptions may move around (e.g., if they are suddenly wrapped in a
StageError).

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

Fix bug introduced in #1384

Co-authored-by: Jim Lawson <ucbjrl@berkeley.edu>

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

Co-authored-by: Jim Lawson <ucbjrl@berkeley.edu>

* Show linking against Javadoc

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

* Add sbt-api-mappings plugin

This adds the sbt-api-mappings plugin which enables
auto-linking (properly setting the apiMappings for the sbt project) so
that Scaldoc/unidoc generation will now automatically link against
Java and Scala API docs (and use the right version).

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

* Show linking against Scala APIs

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

Co-authored-by: Jim Lawson <ucbjrl@berkeley.edu>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

Co-authored-by: Jim Lawson <ucbjrl@berkeley.edu>

No more compile internal

* Rename coreMacros to macros
* Rename chiselFrontend to core

Also make each subproject publish with "chisel3-" as a prefix

This has the effect of causing the coreMacros and chiselFrontend
projects to be published separately

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

Deprecate Driver methods in favor of ChiselStage

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

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

This adds three new methods to ChiselStage to replace deprecated
methods in the Driver for converting a Chisel circuit to a string:
  - emitChirrtl
  - emitFirrtl
  - emitVerilog

This also adds a ChiselStage companion object that lets you generated
a Chisel Circuit or a FIRRTL Circuit from a Chisel module:
  - elaborate
  - convert

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

squash! Add string emission helper methods to ChiselStage

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

* Remove toNamed (and friends) deprecation.

* Add inadvertently deleted leading double quote.

* Remove commented out deprecations.

Add trait chisel3.experimental.NoChiselNamePrefix which causes
@chiselName to skip naming of the instance effectively preventing it
from prefixing any vals inside the instance. It can be applied to
classes such that all instances of that class have this property, or to
individual instances (via creating an anonymous class inline).

Also add basic ScalaDoc for NoChiselNamePrefix and chiselName.

Change the logic for determining which nested ChiselException cause to
use for a trimmed stack trace. Previously, this would use the
outermost. This commit changes this to use the innermost.

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

Don't wrap elaboration annotations

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

Change ChiselException.builderName to compute the name of Chisel's
internal Builder as opposed to hard-coding this with a string.

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

Co-authored-by: Jack Koenig <koenig@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@ibm.com>

Adds two tests:

  1. Test that an internal requirement failure (a bare exception) inside
     a Builder is properly reported/trimmed by ChsielStage/ChiselMain
  2. Test that the full stack trace includes the ChiselException

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

Changes the behavior of ChiselException stack trace trimming to use
either the first exception that includes a method from the Builder or
the outer exception.

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

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

squash! Wrap elaboration in ChiselException

Make mergify open backport PRs & signal on failed cherry-picks

Overriding will always result in a NullPointerException

Introduces mutually-exclusive traits RequireAsyncReset and
RequireSyncReset to set the type of the implicit reset in
MultiIOModules. The Scala-type remains Reset, but the Chisel
elaboration-time checks apply.

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

* Clean up aspects

* Refactored InjectingAspect with InjectorAspect

* Made AspectLibrary work with objects

* Cleaned up code

* Apply suggestions from code review

* Added tests, removed deprecated newInstance call

* Backed out removal of newInstance as exceptions were different

* Removed trailing commas

The release process uses python to scan and set expected versions for a release. The `val defaultVersions = ` stanza should be present for this to work.