User guide

17-29
Using the PLI
• +multisource_int_delays or +transport_int_delays
because interconnect delays need global ACC capabilities.
If you enter the +applylearn compile-time option more than once
on the vcs command line, VCS ignores all but the first one.
Using VPI Routines
To enable VPI capabilities in VCS, you must include the +vpi
compile-time option. For example:
vcs +vpi test.v -P test.tab test.c
The header file for the VPI routines is $VCS_HOME/include/
vpi_user.h.
You can register your user defined system tasks/function-related
callbacks using the vpi_register_systf VPI routine, see "Support for
the vpi_register_systf Routine" on page 17-31.
You can also use a PLI .tab file to associate your user defined system
tasks with your VPI routines, see "PLI Table File for VPI Routines" on
page 17-32.
VCS has not implemented everything specified for VPI routines in the
IEEE Verilog language reference manual because some routines
would be rarely used and some of the data access operations of other
routines would be rarely used. The unimplemented routines are as
follows:
• vpi_get_data
• vpi_put_data
• vpi_sim_control