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
Describe the bug
Using an assert fmt string can fail when codegening something that doesn't generate registers. Even if you specify a reset, the current behavior means it won't be populated unless there's a user. The way op overrides add an assert format string means that it won't look like a reset user at block conversion. You end up with an error like: Assert format string has {rst} placeholder, but block has no reset signal..
To Reproduce
Steps to reproduce the behavior:
Make a function with an assertion that will codegen with no registers (e.g. set pipeline_stages=1)
Run codegen with an assert format string that uses {rst}.
See error
Expected behavior
This should codegen properly with a reset port that gets sent to the assert fmt string.
The text was updated successfully, but these errors were encountered:
Describe the bug
Using an assert fmt string can fail when codegening something that doesn't generate registers. Even if you specify a reset, the current behavior means it won't be populated unless there's a user. The way op overrides add an assert format string means that it won't look like a reset user at block conversion. You end up with an error like:
Assert format string has {rst} placeholder, but block has no reset signal.
.To Reproduce
Steps to reproduce the behavior:
pipeline_stages=1
){rst}
.Expected behavior
This should codegen properly with a reset port that gets sent to the assert fmt string.
The text was updated successfully, but these errors were encountered: