Closed christiaanb closed 8 months ago
There are two work-arounds/fixes:
unsafeToReset
and unsafeFromReset
to be declaration primitives instead of expression primitive, like their VHDL counterparts. This results in Core that doesn't have a let-expression as an argument in an expression.I have implemented 1, which seems like the better approach.
We've released v1.8.0, which includes a fix for this issue.
On CI we can see the
ClockWizard
test fails: https://gitlab.com/clash-lang/clash-compiler/-/jobs/5450795505The underlying reason is that the generated Verilog contains multiple definitions of
result
:Looking at the Core after flattening, the culprit seems to be:
Where we have a let-expression as an argument in an application.