User guide

D-16
Compiler Directives and System Tasks
tasks both generated simulation history files for LSI certification
and had identical syntax except for the name of the system task.
Syntax of the $dumpports system task is now:
$dumpports(module_instance,[module_instance,]
"filename");
You can specify more than one module instance.
Code example:
$dumpports(top.middle1,top.middle2,
"dumports.evcd");
If your source code contains a $dumpports system task and you
want it to generate simulation history files for LSI certification,
include the +dumpports+lsi runtime option.
$dumpportsoff
Suspends writing to files specified in $lsi_dumpports or
$dumpports system tasks. You can specify a file to which VCS
suspends writing or specify no particular file, in which case VCS
suspends writing to all files specified by $lsi_dumpports or
$dumpports system tasks. See IEEE Std 1364-2001 page 340-
341. Syntax:
$dumpportsoff("filename");
$dumpportson
Resumes writing to the file after writing was suspended by a
$dumpportsoff system task. You can specify the file to which
you want VCS to resume writing or specify no particular file, in
which case VCS resumes writing to all files to which writing was
halted by any $dumpportsoff or $dumpports system tasks.
See IEEE Std 1364-2001 page 340-341. Syntax:
$dumpportson("filename");