User guide

3-29
Compiling and Elaborating Your Design
Note:
• 64-bit machines have more capacity than 32-bit machines, but
there is a performance trade-off.
• The process of compiling on a 64-bit machine and simulating the
executable on a 32-bit machine, generally known as Cross-
compilation is not yet supported.
• The 64-bit compilation and 64-32-bit cross-compilation processes
are not available on all platforms, and not all features and
capabilities of VCS work with them. Specific requirements can
change with each release so check this information in the VCS
Release Notes ($VCS_HOME/Doc/ReleaseNotes).
• You can include PLI code in either the 64-32-bit cross-compilation
or full 64-bit compilation processes. PLI code compiled with gcc
usually works fine without any restrictions. Do not forget to compile
the PLI code in 64-bit mode to use it with VCS MX for 64-bit
compilation.
Identifying the Source of Memory Consumption
Before running a 64-32-bit cross-compilation or full 64-bit compilation
process, there are some steps you can take to identify and possibly
solve a memory consumption problem.
If VCS encounters a memory problem during compile-time or runtime,
it typically returns one of the following error messages:
Error: out of virtual memory (swap space)
(v2ss1_16384x64cm16_func.v line 1053458)
Error: malloc(1937887600) returned 0: Not enough space
Doing SDF annotation .......