Skip to content
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

Non-vector timing loop warning #629

veripoolbot opened this issue Mar 7, 2013 · 0 comments

Non-vector timing loop warning #629

veripoolbot opened this issue Mar 7, 2013 · 0 comments


Copy link

@veripoolbot veripoolbot commented Mar 7, 2013

Author Name: Ed Lander
Original Redmine Issue: 629 from
Original Date: 2013-03-07

Capturing forum discussion thread as formal enhancement request (to be discussed with Jeremy) ...

I've attached the example that is upsetting Verilator, which we believe to be an invalid Warning. It's a simplified example of code in our design that Verilator is unhappy with. It's essentially nested conditional statements within a single always block, some assigning values to a variable (sig_c_2) that is called by a function, which changes the value of one of the variables that is tested in the always block (sig_c_1).

Reiterating our theory:

 * sig_c_1 is derived from a function calling sig_c_2
 * sig_c_2 is being evaluated in the always block where there is a test for sig_c_1

However the result of the test for sig_c_1 isn't resulting in an assignment to itself or sig_c_2.

It's clear that reworking Verilator to break this loop would require some major effort, and we are aware that Jeremy is already working on loop detection and reporting. Please consider this ticket a placeholder for (near) future discussion.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.