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
Exception in thread "main" chisel3.package$ChiselException: Connection between left (Foo.w2: Wire[MyBundle]) and source (Foo.w1: Wire[MyBundle]) failed @.foo: Locally unclear whether Left or Right (both internal)
Now this seems obvious. Of course it fails, it has always failed for <> of wires right? Wellllll sort of. The special emission of FIRRTL bulk connect when possible actually makes this legal if val foo were Flipped instead of Input, and user code relies on this behavior sometimes. The reason is an overly pessimistic check here [1] that should only care about direction being Input if the sink is a port (so the fix is super easy).
I wouldn't bother even reporting this but #4205 exposes some cases because it means the Bundle with Flipped now has Input direction (whereas previously it incorrectly had Bidirectional(_) direction.
What is the expected behavior?
This connection should work to prevent #4205 from breaking things.
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 Chisel:
What is the current behavior?
This fails with:
Now this seems obvious. Of course it fails, it has always failed for
<>
of wires right? Wellllll sort of. The special emission of FIRRTL bulk connect when possible actually makes this legal ifval foo
wereFlipped
instead ofInput
, and user code relies on this behavior sometimes. The reason is an overly pessimistic check here [1] that should only care about direction being Input if thesink
is a port (so the fix is super easy).I wouldn't bother even reporting this but #4205 exposes some cases because it means the Bundle with
Flipped
now hasInput
direction (whereas previously it incorrectly hadBidirectional(_)
direction.What is the expected behavior?
This connection should work to prevent #4205 from breaking things.
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: