2.4 Stacks and Stack Sizes

The executing program maintains a main stack for the initial (or main) thread executing the program, as well as distinct stacks for each slave thread. Stacks are temporary memory address spaces used to hold arguments and automatic variables during invocation of a subprogram or function reference. Stack overflow might occur if the size of a thread's stack is too small, causing silent data corruption or a segmentation fault.

Compiling Fortran programs with the f95 -stackvar option forces the allocation of local variables and arrays on the stack as if they were automatic variables. Use of -stackvar with OpenMP programs is implied with explicitly parallelized programs because it improves the optimizer’s ability to parallelize loops with calls. (See the Fortran User’s Guide for a discussion of the -stackvar flag.) However, this usage could lead to stack overflow if not enough memory is allocated for the stack.

Use the limit C-shell command or the ulimit Bourne or Korn shell command to display or set the stack size for the initial (or main) thread. In general, the default stack size for the initial thread is 8 Megabytes.

Each slave thread of an OpenMP program has its own thread stack. This stack mimics the initial (or main) thread stack but is unique to the thread. The thread’s PRIVATE arrays and variables (local to the thread) are allocated on the thread stack. The default size is 4 Megabytes on 32-bit SPARC V8 and x86 platforms, and 8 Megabytes on 64-bit SPARC V9 and x86 platforms. The size of the slave thread stack is set with the OMP_STACKSIZE environment variable.

demo% setenv OMP_STACKSIZE 16384   <-Set thread stack size to 16 Mb (C shell)

demo$ OMP_STACKSIZE=16384   <-Set thread stack size to 16 Mb (Bourne/Korn shell)
demo$ export OMP_STACKSIZE

To detect stack overflows, compile your Fortran, C, or C++ programs with the -xcheck=stkovf compiler option to force a segmentation fault on stack overflow, thereby stopping the program before any data corruption can occur.