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
{{ message }}
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.
@jackkoenig reported that:
I think the issue is that chisel3 or chiseltest is unable to handle unspecified fields in the Bundle literal (DontCare's don't have a litValue which is why you're seeing a None.get). Now because pool is zero-width, you can't specify it because then it doesn't exist and you'll get a different error (an assertion failure that should give a nicer error message)
The text was updated successfully, but these errors were encountered:
I’ve been facing the sane issue and came up with the following workaround: #552
Implicit/automatic handling of zero-width data would definitely look cleaner, but I don’t know of a clean and reliable way that works across all backends.
When running a test with a Bundle with zero-width elements, a fatal None.get error message is reported.
This Scastie reproduces the issue:
https://scastie.scala-lang.org/hutch31/lV9nKmAWRluQ4YTPI2EZ0A/10
@jackkoenig reported that:
I think the issue is that chisel3 or chiseltest is unable to handle unspecified fields in the Bundle literal (DontCare's don't have a litValue which is why you're seeing a None.get). Now because pool is zero-width, you can't specify it because then it doesn't exist and you'll get a different error (an assertion failure that should give a nicer error message)
The text was updated successfully, but these errors were encountered: