vcs对verdi 的database提前编译

 VCS uses VCS compiler scripts to compile the Knowledge Database (KDB) for Verdi. Consequently,

only one common compiler script needs to be maintained for both VCS and Verdi, ensuring consistency between the two databases.

1. add the -kdb option in compile phase to the command line to generate the KDB.

When you specify the –kdb option, Unified Compile front end creates the Verdi KDB and dumps the design into the libraries specified in the synopsys_sim.setup file.

example :

 vcs -kdb <compile_options> <source files>

To generate only the Verdi KDB and skip the simulation database generation, specify the following argument with the -kdb option:
-kdb=only
Generates only the Verdi KDB that is required for both post-process and interactive simulation debug with Verdi.

this option does not generate the VCS compile data/executable, and does not disturb the existing VCS compile data/executables.

For example,

% vcs -kdb=only <compile_options> <source files>

2. Reading Compiled Design with Verdi

To read a compiled design, add the -simflow option to the Verdi command line. This imports the KDB compiled by the Unified Compile front end and enables Verdi and its utilities to use the library mapping from the synopsys_sim.setup file. It is also used to import the design from the KDB library paths.

-dbdir <path>

 ensure that VCS and Verdi use the same data from the synopsys_sim.setup file.

 The <path> argument points to the library directory from where VCS is compiled. Use this option if you

want to invoke Verdi from a working directory that is different from the VCS working directory.

Import KDB:

% verdi -simflow -dbdir <path> -top top -nologo &

summy:

 1. In VCS compile option add ”-lca -kdb“​。

 2. Use ”Verdi -elab simv.daidir/kdb“invoke Verdi。

https://blog.csdn.net/w40306030072/article/details/26280443