User guide

3-31
Compiling and Elaborating Your Design
• Avoid using debug options like -debug, -debug_all...
switches.
• In the pli.tab files, beware of ACC calls that call for global access
(i.e. acc=rw:*)
• Minimize the amount of dumping. Instead of dumping the whole
design, try to limit the scope of dumping to particular modules.
Note that an overhead is incurred if you compile in dumping using
$test$plusargs, even if it is not enabled until runtime.
• If dumping to a VPD file, use +nocelldefinepli+n to limit
dumping to non-library modules.
Contact [e-mail] for details on using these
methods.
Running a 64-32-Bit Cross-Compilation
If you continue to encounter compile-time memory consumption
issues, even after trying the previous methods, then your next step
is to try the 64-32-bit cross-compilation process. This process
compiles a design using a 64-bit address range, which allows the
compilation process to go beyond the 4 GB limit of a 32-bit application.
This process produces a simv that is a 32-bit executable, which
enables you to use your existing 32-bit PLI code and third-party
applications during the simulation.