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
See #�. I think it would be better to have some kind of breadcrumb when Verilator says "Verilated Model did not converge". Ideally it would describe the loop to you, but since this is value dependant, that could turn into some gnarly error messages. Instead, it should probably:
Mention a source line number and not a line number/file name of emitted C++
Tell the user via STDERR how to proceed (i.e. OPT=-DVL_DEBUG and then whatever is next)
I'm only now realizing after digging into this some that the line number in the emitted C++ is pointing me to #2. But I'm guessing most people starting out with the tool wouldn't dig this far or know what they were looking at.
The text was updated successfully, but these errors were encountered:
Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-10-16T00:45:58Z
Looked at this briefly. Currently where V3Emit prints FILE for the "can't converge" error message, there's no good alternative fileline() to print instead. Think we probably should figure out how to use the fileline of the first AstChangeDet. Not sure if this is better done in V3EmitC or when make _change_detect in V3Change.cpp
Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 1556 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
See #�. I think it would be better to have some kind of breadcrumb when Verilator says "Verilated Model did not converge". Ideally it would describe the loop to you, but since this is value dependant, that could turn into some gnarly error messages. Instead, it should probably:
I'm only now realizing after digging into this some that the line number in the emitted C++ is pointing me to #2. But I'm guessing most people starting out with the tool wouldn't dig this far or know what they were looking at.
The text was updated successfully, but these errors were encountered: