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

Include the function being called in the suggestion.

Remove reflective naming

With reflective naming removed, this warning no longer does anything so
the option to enable it is deprecated.

This includes removal of closeUnboundIds and _onModuleClose which were
hacks to support naming of non-hardware (ie. unbound) Data.

This can result in a substantial performance improvement for large
Modules with many public vals.

This includes both .*Name APIs and .toTarget

Add --warn:reflective-naming

This new argument (and associated annotation) will turn on a warning
whenever reflective naming changes the name of a signal. This is
provided to help migrate from Chisel 3.5 to 3.6 since reflective naming
is removed in Chisel 3.6.

The new function is chisel3.internal.buildName.

Previously, verification statements (assert, assume, cover, and printf)
were only named via reflection.

This is a formatted version of the p"..." interpolator analogous to
Scala's f"..." interpolator. The primary difference is that it supports
formatting interpolated variables by following the variable with
"%<specifier>". For example:

printf(cf"myWire = $myWire%x\n")

This will format the hardware value "myWire" as a hexidecimal value in
the emitted Verilog. Note that literal "%" must be escaped as "%%".

Scala types and format specifiers are supported and are handled in the
same manner as in standard Scala f"..." interpolators.

This includes (and is tested) for both the old .*Name APIs and
.toTarget

ExtModule now uses the same namePorts implementation as regular Modules.
Previously, ExtModules only allowed port naming via runtime reflection.
This meant that .suggestName and other naming APIs do not work. It also
breaks FlatIO for ExtModule which is a potential replacement API for
BlackBox's special `val io` handling.

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

This required implementing _elementsImpl manually for all HWTuple
classes (which do not have the plugin run on them).

Move stdlib.test to integration test.

* Add BarrelShifter API for Vec

* Add BarrelShifter Test

* fix for build.sc

* Fix package name and move file

* Fix sbt for stdlib

Co-authored-by: Jiuyang Liu <liu@jiuyang.me>

* add standard library project

* add stdlib to mill build system.

* CI success needs stdlib test pass.

Co-authored-by: Kevin Läufer <laeufer@cs.berkeley.edu>

* WIP: Add BitSetRange

* BitSetRange: various code format changes

* Try to fix scala random versioning

* Initial impl of BitSet.toRange, along with some helper method in BitSet

* BitPatRange: visibility and name changes:

* BitSetRange: tests

* BitSetRange: remove Random.between

* Move BitSetRange to BitSet.fromRange. Remove BitSetRange and toBitSetRanges

* Rename max_known_length -> MaxKnownLength in BitPat

* Apply suggestions from code review

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

* add api fromRange(start:  BigInt, length: BigInt)

Co-authored-by: Jiuyang Liu <liu@jiuyang.me>
Co-authored-by: Jack Koenig <jack.koenig3@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* Cat: add source locators

* make test handle both cases

* test that the wrong source locator is not included for Cat

* Add source locators to FillInterleaved and test

* Add Bitwise Spec

* add FillSpec

* Reverse Spec

* Checkpoint -- doesn't compile

* Make source locators more correct with do_apply methods

* add source locators to Reg.scala

* RegEnable source locator tests

* ShiftRegisters source locators unit tests

* scalafmt

* clean up spacing and final defs

* scalafmt

* scaladoc groups

All functions inside this package were deprecated
in the 3.5 release, so it is appropriate to remove
them for 3.6

* Update scalatest to 3.2.12

* Revert commit(s) 20a9de1f

* Update scalatest to 3.2.12

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

For traits or abstract classes that extend Bundle but have no concrete
methods, the plugin will print a benign warning that the user cannot
fix. It will no longer print that warning.

In Scala 2.13, Auto-application to `()` is deprecated. Any nullary
method (ie. a method with no arguments) that is defined with () must now
be called with (). @chiselName used to inject a case of this warning
into user code which would then cause a warning on the @chiselName macro
that the user has no way to fix.

The difference in logic depth for various paths now has a maximum of 1.

Also make treeReduce order the same for 2.12 and 2.13

.grouped(_) returns an Iterator
.toSeq on an Iterator returns a Stream in 2.12 and a List in 2.13
This can lead to changes in order when bumping from 2.12 to 2.13 that
can be avoided by simply using an eager collection explicitly.

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

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