We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With a somewhat older clash, namely
clash
$ ~/.cabal/bin/clash --version CAES Language for Synchronous Hardware, version 0.6.8 (using clash-lib, version: 0.6.8)
I observed that a topEntity with a non-function signature
topEntity
topEntity :: Signal (SFixed 2 10)
will not get a testbench generated even if I have
expectedOutput :: Signal (SFixed 2 10) -> Signal Bool expectedOutput = outputVerifier $(v ...)
available. I tricked it into submission by giving topEntity a dummy input signal, but ignoring it:
topEntity :: Signal Bool -> Signal (SFixed 2 10) topEntity _ = ... as before ...
For
CAES Language for Synchronous Hardware, version 0.6.15 (using clash-lib, version : 0.6.13)
this trick does not work any more. What can I do?
The text was updated successfully, but these errors were encountered:
I ended up always inputting a False signal and using mux. But this is not very satisfactory :-(
False
mux
Sorry, something went wrong.
7ec8fe4
Test benches will now also be generated for circuits that have no inputs. I'll release a new version of clash containing this feature today.
No branches or pull requests
With a somewhat older
clash
, namelyI observed that a
topEntity
with a non-function signaturewill not get a testbench generated even if I have
available. I tricked it into submission by giving
topEntity
a dummy input signal, but ignoring it:For
this trick does not work any more. What can I do?
The text was updated successfully, but these errors were encountered: