Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
More informative did not converge message #1556
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.
Original Redmine Comment
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