New issue
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
Adding failing test case for source synchronous signals #3038
Conversation
Let me know if you would like me to raise an issue for tracking as well! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
endmodule |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the test should somehow check that the clocker attribute is honored.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I was having trouble with that. Basically the problem was that Verilator is normally good about inferring the source synchronous signal for small designs. Only my large complex design suddenly started having problems (always_ff @(s.clk) not triggering, etc.)
So when I wrote a test that actually exercised this, it spuriously passed
Co-authored-by: Wilson Snyder <wsnyder@wsnyder.org>
Done! |
Please see the test failure - maybe need to update .out? |
Yep, there was a whitespace issue on the .out file, sorry about that. Should be good to go now! |
Source-synchronous structs are a common construct. With complex code, Verilator does not detect the clock signal in the struct as a clock. Trying to fix this with a clocker pragma results in the following error, exposed by this test case: