User guide

25-22
Source Protection
// No. of user function calls: 0 0
// No. of hierarchical references: 0 0
// No. of concatenations: 0 0
// No. of force/release statements: 0 0
// No. of bit selects: 0 0
// No. of part selects: 1 1
// No. of non-blocking assignments: 0 0
// No. of specify blocks<#>: 0 0
// No. of timing checks: 0 0
//
// No. of top level modules: 1
// modules: 1
// No. of udps: 0
// seq. udps: 0
// comb. udps: 0
// No. of module+udp ports: 2
// No. of system tasks: 1
// No. of user tasks: 0
// No. of system functions: 0
// No. of user functions: 0
//
// Footnotes:
// ---------
// <!> No. of unique instances of a construct as it appears
// in the source.
// <@> No. of instances of a construct when the design //
is elaborated.
// <#> Multiple specify blocks in the SAME module are //
combined and counted as ONE block.
Note: If you are creating a mangled tokens.v file to send to Synopsys
for technical support, we advise checking to see if you can
duplicate the problem using the tokens.v file. Also please include
with this file a copy of the vcs and simv command lines that
duplicate the problem and any SDF files that need to be back
annotated and C source files or object files for PLI applications
that need to be linked to the simv executable.