Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn on S-interpolator usage for assert, assume and printf (backport #2751) #2756

Conversation

adkian-sifive
Copy link
Contributor

Manual backport of #2751, change errors to warnings

Contributor Checklist

  • Did you add Scaladoc to every public function/method?
  • Did you add at least one test demonstrating the PR?
  • Did you delete any extraneous printlns/debugging code?
  • Did you specify the type of improvement?
  • Did you add appropriate documentation in docs/src?
  • Did you state the API impact?
  • Did you specify the code generation impact?
  • Did you request a desired merge strategy?
  • Did you add text to be included in the Release Notes for this change?

Type of Improvement

API Impact

Backend Code Generation Impact

Desired Merge Strategy

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels?
  • Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

seldridge and others added 30 commits January 13, 2021 21:02
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Add a "handover" option that augments circt.stage.ChiselStage to lower
using a combination of the Scala FIRRTL Compiler (SFC) followed by
CIRCT.  The handover can be set at CHIRRTL (don't run the SFC), High
FIRRTL, Middle FIRRTL, Low FIRRTL, or Optimized Low FIRRTL.

Include tests of this behavior by looking at the
FirrtlCircuitAnnotation that exists before running CIRCT for different
handover values.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
…able-handover

Add --handover option to lower partially using SFC
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
- Add Maven release, Sonatype snapshots, and Javadoc.io badges
- Improve setup instructions

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Add an option to output using a "*.v" suffix.  This is still using the
CIRCT SystemVerilog back end, though.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Change command line option passed to "firtool" due to upstream change.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
* Enable CI for 3.5.x branch
* Enable Mergify for 3.5.x branch
* Drop 3.5.x from Mergify
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
* add mill build system
* bump to Chisel 3.5.0
* use cross build to select Scala version.
* add gitignore
* Add/use Compiler Plugin
…iance#2352)

This only includes a merge-based flow which will presumably be
squash-and-merged for any merged PRs. It is possible to do this with
rebasing but it is tricky and hard to describe in a fool-proof way.
#naming implies within the current file. Removing the # refers to a file in the current directory.
The new reflection based IO autowrapping for compatibility mode Modules
would previously throw a NullPointerExceptions if any hardware were
constructed in the Module before "val io" was initialized. The logic is
now more robust for this case.

Co-authored-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* Fix the QMC bug for constant and dontcare output.
* Fix the Espresso bug for constant and dontcare output.
sequencer and others added 28 commits September 6, 2022 14:17
Co-authored-by: Jack Koenig <koenig@sifive.com>
Add macro for determining Chisel structural subtypes. This replaces the                                                                                                                                                       
use of built-in <:< for determining what types can be cast with
.viewAsSuperType.
* Cleanup Cookbook and printing docs
* Format specifiers are actually concise now

Co-authored-by: Megan Wachs <megan@sifive.com>
This enables emission of modules that serialize to >2 GiB of .fir text.
)

Previously, failed jobs in the CI matrix would cause the sentinel job
(all-tests-passed) to be skipped, which for purposes of Github Actions
branch protection would count as "success". This allowed PRs with
failing CI to be merged. This new approach which uses two sentinel jobs
should not suffer from this same issue.
The command line options for CIRCT's firtool command have been updated.
Treadle will be used as the "defaultBackend" when the environment
variable CHISEL3_CI_USE_TREADLE is set. The intent is to set this
variable during CI for pre-merge CI (aka on pull requests).
Use Treadle (on pull requests only) to speed up CI
Co-authored-by: Megan Wachs <megan@sifive.com>
Update a callsite. Rename function in Printf.scala to match the naming
convention in the file. Undo call by name change to preserve binary compatibility.
Better docs for the error

Update error message to not mention the p-interpolator
@adkian-sifive
Copy link
Contributor Author

adkian-sifive commented Oct 3, 2022

Chose the wrong source branch, unable to change it on github..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.