You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide the steps to reproduce the problem:
Consider the following example:
//>usingscala"2.13.12"//>usingdep"org.chipsalliance::chisel:6.4.0"//>usingplugin"org.chipsalliance:::chisel-plugin:6.4.0"//>usingoptions"-unchecked", "-deprecation", "-language:reflectiveCalls", "-feature", "-Xcheckinit", "-Xfatal-warnings", "-Ywarn-dead-code", "-Ywarn-unused", "-Ymacro-annotations"importchisel3._importchisel3.probe._// _root_ disambiguates from package chisel3.util.circt if user imports chisel3.util._import_root_.circt.stage.ChiselStageclassFooextendsModule {
valout=IO(Output(Probe(UInt(8.W))))
valw=Wire(UInt(6.W))
define(out, ProbeValue(w))
}
objectMainextendsApp {
println(
ChiselStage.emitSystemVerilog(
gen =newFoo,
firtoolOpts =Array("-disable-all-randomization", "-strip-debug-info")
)
)
}
What is the current behavior?
This errors with:
[error] Users/koenig/work/t/define/chisel-example.scala 16:9: Cannot define a probe on a non-equivalent type.
[error] There were 1 error(s) during hardware elaboration.
What is the expected behavior?
It would be nice if the error message would include some information about how the types differ. This is especially important for Bundles with mismatched fields deeply nested.
Please tell us about your environment:
Other Information
What is the use case for changing the behavior?
The text was updated successfully, but these errors were encountered:
Type of issue: Bug Report
Please provide the steps to reproduce the problem:
Consider the following example:
What is the current behavior?
This errors with:
What is the expected behavior?
It would be nice if the error message would include some information about how the types differ. This is especially important for Bundles with mismatched fields deeply nested.
Please tell us about your environment:
Other Information
What is the use case for changing the behavior?
The text was updated successfully, but these errors were encountered: