User guide

3-30
Compiling and Elaborating Your Design
Error: malloc(400) returned 0: Not enough space
error: out of virtual memory (swap space)
error: calloc(16384,1) returned 0: Cannot allocate memory
Error-[NOMEM] Out of virtual memory (swap space)!
sbrk(0) returned 0x80f52ea0
datasize limit 2097148 KB
memorysize limit 2097152 KB
If you encounter one of these error messages, there are several
alternative methods you can try that might help adapt to the memory
requirements of your design. These methods, described briefly in the
next section, apply to cases in which you are simulating large, flat,
gate-level designs with no timing or timing checks. If this is not the
case, then you should proceed to the methodology described in
“Running a 64-Bit Compilation and Simulation” on page 3-34.
Minimizing Memory Consumption
The following list contains several ways you can minimize your
compile-time and runtime memory consumption without using the
-full64 or -comp64 options:
• Check the physical memory on your workstation. You can use the
top utility for this. All current operating systems, including Linux,
support 4 GB of memory. Make sure you are using a machine with
enough available memory (that is, even though your machine may
appear to have plenty of memory, if there are other processes
running concurrently on that machine, you won't have access to
the entire memory).