Tywaves annotations #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Create `TywavesAnnotation` (firrtl) case class to represent the annotation
- Add companion object to generate `TywavesChiselAnnotation`s for Chisel circuit: it parses a chisel circuit, extracts the necessary information from each component, and annotates each FIRRTL target
- Support annotation for IO ports
- Add support for modules and data types (grounds, aggregates, and user-defined (only extended bundles))
- Support nested modules and data types
- Create `AddTywavesAnnotations` phase to add the TywavesAnnotation to the elaborated Chisel circuit
- Update `ChiselStage` to integrate `AddTywavesAnnotation` phase (run before `Convert` phase only if `withDebug` is true)
- Added following tests:
- Module tests:
- Empty module
- Module with submodule(s)
- Modules with parameters and paremetrized modules (need to extract scala meta-programming information though)
- BlackBoxes
- Intrinsics
- Classes
- Ports test:
- Explict Clock, SyncReset (Bool), AsyncReset and Reset
- Implicit clock and reset
- Ground types: Bool, UInt, SInt, Analog
- Bundles: empty, anonymous, user-defined, nested
- Vecs: 1-D, 2-D
- MixedVec
- Vecs of bundles
- Bundles of vecs
- Added "createAnno" from DefWire, DefRef, DefRegInit case
- Reorganize test structure making reusable modules for different bindings (IO, Reg, Wire)
- Added following tests:
- Ports tests:
- Ports inside a submodule
- Wire/reg tests:
- Explict Clock, SyncReset (Bool), AsyncReset and Reset
- Implicit clock and reset
- Ground types: Bool, UInt, SInt
- Analog (only wires)
- Bundles: empty, anonymous, user-defined, nested
- Vecs: 1-D, 2-D
- MixedVec
- Vecs of bundles
- Bundles of vecs
- Wires/regs inside a submodule
- Move module and data types tests in different subdirectories - Add readmes with output samples of the annotations
- Added "createAnno" from DefMemory, DefSeqMemory, FirrtlMemory and DefMemPort case
- Implement "createAnnoMem" to create a TyeavesAnnotation for memory (a memory does not extend the Data type)
- Return empty annotations from Connect, DefInvalid
- Add warning message for "Unhandled circuit commands"
- Added the following tests:
- ROM of ground type
- SyncReadMem (when UNUSED) of ground type, aggregate types (bundle)
- Mem (when UNUSED) of ground type, aggregate types (bundle)
- SRAM of ground type (with different combs of ports), aggregate types
- SyncReadMem (when USED) of ground type, aggregate types (this instantiate MPORT)
- Mem (when USED) of ground type, aggregate types (this instantiate MPORT)
…of Vecs) - Added the following tests: - Masked memories (SyncReadMem, Mem, SRAM)
…onstructor (it works for any scala class)
[Fix tywaves] Fix annotation issue for first parameter of the constructor
Sometimes the first parameters was skipped. The `getConstructorParams` was dropping the first element of the list assuming that it contained the class itself and not a parameter.
This assumption worked only for some cases ("$outer" is not always present in first position). Now the method is improved by doing a filter map (collect).
Update report output samples in tests readmes
Annotate types with parameters in the scala constructor (it works for any scala class)
- Create a case class (`ClassParam`) to represent the parameters of a class in the firrtl annotation
- Update `TywavesAnnotation` with `params: Option[Seq[ClassParam]]`. Some classes may not have any parameter
- Implement `getConstructorParams()` to get params of a constructor of any scala class. It uses scala reflection.
- Added the following tests:
- Test getConstructorParams() for:
- classes
- case classes
- private, protected and public fields in the constructor: name, type and value accessible
- fields in the body of a class (expected behaviour not accessible)
- parameters in the constructor (no val): only name and type accessible
- Updated the following tests:
- Vec tests of DataTypesSpec: chisel Vecs have a length parameter in the constructor
- Mem tests: memories contain constructs with parameters in their constructors
- Module tests: update the module with parameters test
…s type of chisel3.Data
Now it returns only the value without the complete name (packageName.type.name) of the parameter.
- Fix hasParams: sometimes some parameters of a class were not detected.
- Added the following tests:
- Circuit with parameters (scala basic types, scala classes, and chisel types)
- Bundles with parameters (scala basic types, scala classes, and chisel types)
- Updated tests (scala fmt and bug fix):
- TypeAnnotationMemSpec
- TypeAnnotationModuleSpec
- TypeAnnotationDataTypesSpec
- Fix scalafmt errors
…nce#4116) Node 16 is deprecated and will eventually stop being supported.
This saves developers from having to install a dependency. It also allows us to drop an old Github Actions dependency that hasn't been updated in 2 years. This is the standard practice for projects using Mill on Github.
…4146) This is an automated commit generated by the `circt/update-circt` GitHub Action. Co-authored-by: chiselbot <chiselbot@users.noreply.github.com>
Add support for `until`, `intersect`, `repeat`, `non_consecutive_repeat`, and `goto_repeat` property operations from SVA.
…alliance#4144) * simulator: add SourceInfo to expect calls and report. * simulator: add test for failed expects. * simulator: attempt to extract source line. * simulator: make testableData.expect's sourceInfo parameter explicit. * simulator: add factory method for giving failed expect sourceInfo/extraContext.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.