Stats

  • Locked Locked
  • Replies 0
  • Subscribers 65
  • Views 2967
  • 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

Performance difference between API (PLI/VPI/DPI), TCL, Verilog functions w.r.t. object browsing/read

Sporadic Crash

Subject explains.

During simulaton runtime, there are three ways to read values of signals:

  • Option 1: accessing objects through TCL command find and reading their values with the TCL command value
  • Option 2: accessing objects through API (PLI/VPI) and reading their values with vpi_get_value or similar
  • Option 3: accesisng objects through language  by $display, $monitor etc.

Advantages in terms of speed/performance

  • Option 1: no need to compile/elaborate. Recursion possible.
  • Option 2: no need to compile/elaborate, faster because you don't TCL interpreter. Recursion possible.
  • Option 3: n/a

Disadvantages

  • Option 1: needs TCL interpreter
  • Option 2: n/a
  • Option 3: requires compilation/elaboration. Recursion is difficult.

Based on the assumptions above, accessing objects through API (PLI/VPI/DPI) is much faster.

Can anybody elaborate this?

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.