-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bad error message when using experimental.IO #1109
Comments
At the very least, Possible [more robust] solutions:
|
Is experimental IO documented anywhere? |
I don't think so, obviously should be |
I found currently used
seems to be an alias to I tested |
@sequencer yeah that's right. The basic idea is that some name must be recording for all values declared as |
Summary of changes in chisel3: * Patch fix to chipsalliance/chisel#1109 Summary of changes in firrtl: * Constant propagate binary operations with matching arguments * Revert last connect semantics support in reset inference * Fix reset inference for Resets that are only invalidated
Summary of changes in chisel3: * Patch fix to chipsalliance/chisel#1109 Summary of changes in firrtl: * Constant propagate binary operations with matching arguments * Revert last connect semantics support in reset inference * Fix reset inference for Resets that are only invalidated
* add multi target annotation for advices * use Seq[Seq[Target]] store targets * add flat function * doc simplify
When using
experimental.IO
as used in many diplomatic libraries, if you forget to.suggestName
the port, you'll get a really unhelpful exception instead of the desired error at https://github.com/freechipsproject/chisel3/blob/410f03b9122978e43db938d7774b451f2b9111d0/chiselFrontend/src/main/scala/chisel3/RawModule.scala#L52.It appears to be due to the improved
.toString
(#985) which during the above error message hits another, less helpful error message.Type of issue: bug report
Impact: no functional change
Development Phase: proposal
Other information
If the current behavior is a bug, please provide the steps to reproduce the problem:
What is the current behavior?
This gives:
What is the expected behavior?
Instead, it should error saying that it couldn't name the IO
The text was updated successfully, but these errors were encountered: