User`s guide

Cray XMT™ Programming Environment User’s Guide

Figure 2. Comparison of Whole-program and Separate-module Modes

Whole-program Compilation

skinny .o Files

Parsed source code

Call graph

Object code

Debugger information

arnoldi.o

blas.o

test

Executable

code

Separate-module Compilation

fat .o Files

Parsed source code

Partial call graph

Object code

Debugger information

blas.o

test.pl

test

Parsed source code

Partial call graph

Object code

Debugger information

Executable

code

test.pl arnoldi.o

In whole-program mode, all the traditional object information for a program is

contained in a single program library file. The program library has a .pl filename

extension. The compilation process also produces an object file with a .o extension

for each source file. This file is used as a time stamp to drive build processes.

Each .o file corresponds to a module contained in the program library. The object

information, or modules, for a program's source files are packaged together. This

enables the compiler to optimize each function within the context of the entire

program.

78 S–2479–20