# fp-stack-check, Qfp-stack-check

Tells the compiler to generate extra code after every function call to ensure that the floating-point stack is in the expected state. This feature is only available for ifort.

## Syntax

Linux: | -fp-stack-check

macOS: | -fp-stack-check

Windows: | /Qfp-stack-check

## Arguments

None

## Default

OFF | There is no checking to ensure that the floating-point (FP) stack is in the expected state.

## Description

This option tells the compiler to generate extra code after every function call to ensure that the floating-point (FP) stack is in the expected state.

By default, there is no checking. So when the FP stack overflows, a NaN value is put into FP calculations and the program's results differ. Unfortunately, the overflow point can be far away from the point of the actual bug. This option places code that causes an access violation exception immediately after an incorrect call occurs, thus making it easier to locate these issues.

## IDE Equivalent

Visual Studio: Floating-Point > Check Floating-Point Stack

## Alternate Options

None

Parent topic: Floating-Point Options