Compiling very large routines (thousands of lines of code in a single procedure) at -xO3 or higher can require a large amount of memory. In such cases, performance of the system might degrade. You can control memory footprint by limiting the amount of virtual memory available to a single process.
To limit virtual memory in an sh shell, use the ulimit command. See the sh(1) man page for more information.
The following example shows how to limit virtual memory to 4 Gbytes:
example$ ulimit -d 4000000
In a csh shell, use the limit command to limit virtual memory. See the csh(1) man page for more information.
The next example also shows how to limit virtual memory to 4 Gbytes:
example% limit datasize 4G
Each of these examples causes the optimizer to try to recover at 4 Gbytes of data space.
The limit on virtual memory cannot be greater than the system’s total available swap space and, in practice, must be small enough to permit normal use of the system while a large compilation is in progress.
Be sure that no compilation consumes more than half the swap space.
With 8 Gbytes of swap space, use the following commands:
In an sh shell:
example$ ulimit -d 4000000
In a csh shell:
example% limit datasize 4G
The best setting depends on the degree of optimization requested and the amount of real memory and virtual memory available.