Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 12933
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IUS 8.2 and Systemverilog-2008 features?

cubicle82

I haven't had the opportunity to upgrade to IUS82 at my workplace.  

I'm interested to know whether IUS82 recognizes the proprocessor-tokens `__LINE__ and `__FILE__?

At the moment we're using a user-linked VPI/DPI to capture&report this debug-info in our verification-libraries, but we're always looking for chances to reduce overhead.

  • I don't know if the very latest 8.2 release supports this, but it wasn't working in early 8.2 versions.

    That said, if you're writing SystemVerilog code, why make life difficult for yourself by writing the error handling printout yourself?
    If you use immediate assertions, then IUS will print the file name, line number and time stamp all on one line automatically, thus:

    ncsim> run
    ncsim: *E,ASRTST (./preproc.sv,15): (time 0 NS) Assertion tb.__assert_1 has failed

    You can get a warning message by using $warning() with the assertion, so that the simulation won't stop or fail because of the assertion.

    And if you use OVM's messaging facility instead of $display(), then you get nice regular message display which you can control without needing to hackcode around to turn the debug on and off...

     

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.