# ipo-jobs, Qipo-jobs

Specifies the number of commands (jobs) to be executed simultaneously during the link phase of Interprocedural Optimization (IPO). This feature is only available for ifort.

## Syntax

Linux: | -ipo-jobs n

macOS: | -ipo-jobs n

Windows: | /Qipo-jobs:n

## Arguments

n | Is the number of commands (jobs) to run simultaneously. The number must be greater than or equal to 1.

## Default

-ipo-jobs1 or /Qipo-jobs:1 | One command (job) is executed in an interprocedural optimization parallel build.

## Description

This option specifies the number of commands (jobs) to be executed simultaneously during the link phase of Interprocedural Optimization (IPO). It should only be used if the link-time compilation is generating more than one object. In this case, each object is generated by a separate compilation, which can be done in parallel.

This option can be affected by the following compiler options:

- [Q]ipo when applications are large enough that the compiler decides to generate multiple object files.

- [Q]ipo n when n is greater than 1.

- [Q]ipo-separate

### CAUTION

Be careful when using this option. On a multi-processor system with lots of memory, it can speed application build time. However, if n is greater than the number of processors, or if there is not enough memory to avoid thrashing, this option can increase application build time.

## IDE Equivalent

None

## Alternate Options

None

Parent topic: Interprocedural Optimization Options

## See Also

ipo, Qipo compiler option
ipo-separate, Qipo-separate compiler option