Project

General

Profile

[logo] 
 
Home
News
Activity
About/Contact
Major Tools
  Dinotrace
  Verilator
  Verilog-mode
  Verilog-Perl
Other Tools
  IPC::Locker
  Parallel::Forker
  Voneline
General Info
  Papers

Issue #1556

More informative did not converge message

Added by Todd Strader about 1 month ago. Updated 13 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Lint
% Done:

0%


Description

See bug1549. 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:
  1. Mention a source line number and not a line number/file name of emitted C++
  2. 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.


Related issues

Related to Issue #1549: Verilated Model did not DC converge NoFixNeeded

History

#1 Updated by Todd Strader about 1 month ago

  • Related to Issue #1549: Verilated Model did not DC converge added

#2 Updated by Wilson Snyder about 1 month ago

  • Category set to Lint
  • Status changed from New to Feature

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

#3 Updated by Wilson Snyder 13 days ago

  • Status changed from Feature to Closed
  • Assignee set to Wilson Snyder

Not perfect (still not great line number), but a lot more trail to follow now.

Also available in: Atom