One of my more frequent rants, both online and in person, is the danger posed by the "fastmath" compiler flag. While these rants may elicit resigned acknowledgment from those who already understand the dangers involved, they do little to help those who don't. So given the remarkable paucity of writing on the topic (including the documentation of the compilers themselves), I decided it would make a good inaugural topic for this blog.
It's a compiler flag or option that exists in many languages and compilers, including:
fpmodel=fast
(the default) in ICC
/fp:fast
in MSVC
mathmode=fast
command line option or @fastmath
macro in Julia.
So what does it actually do? Well, as the name said, it makes your math faster. That sounds great, we should definitely do that!
I mean, the whole point of fastmath is trading off speed with correctness. If fastmath was to give always the correct results, it wouldn’t be fastmath, it would be the standard way of doing math.
The rules of floating point operations are specified in the IEEE 754 standard, which all popular programming languages (mostly) adhere to; compilers are only allowed to perform optimizations which obey these rules. Fastmath allows the compiler to break some of these rules: these breakages may seem pretty innocuous at first glance, but can have significant and occasionally unfortunate downstream effects.
In GCC, ffastmath
(or Ofast
) enables the following options: fnomatherrno
, funsafemathoptimizations
, ffinitemathonly
, fnoroundingmath
, fnosignalingnans
, fcxlimitedrange
and fexcessprecision=fast
. Note that funsafemathoptimizations
is itself a collection of options fnosignedzeros
, fnotrappingmath
, fassociativemath
and freciprocalmath
, plus some extra ones, which we will discuss further below.
Now some of these are unlikely to cause problems in most cases: fnomatherrno
^{[1]}, fnosignalingnans
, fnotrappingmath
disable rarelyused (and poorly supported) features. Others, such as freciprocalmath
can reduce accuracy slightly, but are unlikely to cause problems in most cases.
Krister Walfridsson gives a very nice (and somewhat more objective) description of some of these, but I want to focus on three in particular.
ffinitemathonly
Allow optimizations for floatingpoint arithmetic that assume that arguments and results are not NaNs or +Infs.
The intention here is to allow the compiler to perform some extra optimizations that would not be correct if NaNs or Infs were present: for example the condition x == x
can be assumed to always be true (it evaluates false if x
is a NaN).
This sounds great! My code doesn't generate any NaNs or Infs, so this shouldn't cause any problems.
But what if your code doesn't generate any intermediate NaNs only because it internally calls isnan
to ensure that they are correctly handled?
— based on an example from John Regehr
(to explain what this is showing: the function is setting the return register eax
to zero, by xor
ing it with itself, which means the function will always return false
)
That's right, your compiler has just removed all those checks.
Depending on who you ask, this is either obvious ("you told the compiler there were no NaNs, so why does it need to check?") or ridiculous ("how can we safely optimize away NaNs if we can't check for them?"). Even compiler developers can't agree.
This is perhaps the single most frequent cause of fastmathrelated StackOverflow questions and GitHub bug reports, and so if your fastmathcompiled code is giving wrong results, the very first thing you should do is disable this option (fnofinitemathonly
).
fassociativemath
Allow reassociation of operands in series of floatingpoint operations.
This allows the compiler to change the order of evaluation in a sequence of floating point operations. For example if you have an expression (a + b) + c
, it can evaluate it instead as a + (b + c)
. While these are mathematically equivalent with real numbers, they aren't equivalent in floating point arithmetic: the errors they incur can be different, in some cases quite significantly so:
julia> a = 1e9+1; b = 1e9; c = 0.1;
julia> (a+b)+c
1.1
julia> a+(b+c)
1.100000023841858
So why would you want to do this? One primary reason is that it can enable use of vector/SIMD instructions:
For those who aren't familiar with SIMD operations (or reading assembly), I'll try to explain briefly what is going on here (others can skip this part). Since raw clock speeds haven't been getting much faster, one way in which processors have been able to increase performance is through operations which operate on a "vector" (basically, a short sequence of values contiguous in memory).
In this case, instead of performing a sequence of floating point additions (addss
), it is able to make use of a SIMD instruction (addps
) which takes vector float
s (4 in this case, but it can be up to 16 with AVX 512 instructions), and adds them elementwise to another vector in one operation. It does this for the whole array, followed by a final reduction step where to sum the vector to a single value. This means that instead of evaluating
s = arr[0] + arr[1];
s = s + arr[2];
s = s + arr[3];
...
s = s + arr[255];
it is actually doing
s0 = arr[0] + arr[4]; s1 = arr[1] + arr[5]; s2 = arr[2] + arr[6]; s3 = arr[3] + arr[7];
s0 = s0 + arr[8]; s1 = s1 + arr[9]; s2 = s2 + arr[10]; s3 = s3 + arr[11]);
...
s0 = s0 + arr[252]; s1 = s1 + arr[253]; s2 = s2 + arr[254]; s3 = s3 + arr[255]);
sa = s0 + s1;
sb = s2 + s3;
s = sa + sb;
where each line corresponds to one floating point instruction.
The problem here is that the compiler generally isn't allowed to make this optimization: it requires evaluating the sum in a different association grouping than was specified in the code, and so can give different results^{[2]}. Though in this case it is likely harmless (or may even improve accuracy^{[3]}), this is not always the case.
Certain algorithms however depend very strictly on the order in which floating point operations are performed. In particular compensated arithmetic operations make use of it to compute the error that is incurred in intermediate calculations, and correct for that in later computations.
The most wellknown algorithm which makes use of this is Kahan summation, which corrects for the round off error incurred at addition step in the summation loop. We can compile an implementation of Kahan summation with ffastmath
, and compare the result to the simple loop summation above:
It gives exactly the same assembly as the original summation code above. Why?
If you substitute the expression for t
into c
, you get
c = ((s + y)  s)  y);
and by applying reassociation, the compiler will then determine that c
is in fact always zero, and so may be completely removed. Following this logic further, y = arr[i]
and so the inside of the loop is simply
s = s + arr[i];
and hence it "optimizes" identically to the simple summation loop above.
This might seem like a minor tradeoff, but compensated arithmetic is often used to implement core math functions, such as trigonometric and exponential functions. Allowing the compiler to reassociate inside these can give catastrophically wrong answers.
This one is the most subtle, but by far the most insidious, as it can affect code compiled without fastmath, and is only cryptically documented under funsafemathoptimizations
:
When used at link time, it may include libraries or startup files that change the default FPU control word or other similar optimizations.
So what does that mean? Well this is referring to one of those slightly annoying edge cases of floating point numbers, subnormals (sometimes called denormals). Wikipedia gives a decent overview, but for our purposes the main thing you need to know is (a) they're very close to zero, and (b) when encountered, they can incur a significant performance penalty on many processors^{[4]}.
A simple solution to this problem is "flush to zero" (FTZ): that is, if a result would return a subnormal value, return zero instead. This is actually fine for a lot of use cases, and this setting is commonly used in audio and graphics applications. But there are plenty of use cases where it isn't fine: FTZ breaks some important floating point error analysis results, such as Sterbenz' Lemma, and so unexpected results (such as iterative algorithms failing to converge) may occur.
The problem is how FTZ actually implemented on most hardware: it is not set perinstruction, but instead controlled by the floating point environment: more specifically, it is controlled by the floating point control register, which on most systems is set at the thread level: enabling FTZ will affect all other operations in the same thread.
GCC with funsafemathoptimizations
enables FTZ (and its close relation, denormalsarezero, or DAZ), even when building shared libraries. That means simply loading a shared library can change the results in completely unrelated code, which is a fun debugging experience.
I've joked on Twitter that "friends don't let friends use fastmath", but with the luxury of a longer format, I will concede that it has valid use cases, and can actually give valuable performance improvements; as SIMD lanes get wider and instructions get fancier, the value of these optimizations will only increase. At the very least, it can provide a useful reference for what performance is left on the table. So when and how can it be safely used?
One reason is if you don't care about the accuracy of the results: I come from a scientific computing background where the primary output of a program is a bunch of numbers. But floating point arithmetic is used in many domains where that is not the case, such as audio, graphics, games, and machine learning. I'm not particularly familiar with requirements in these domains, but there is an interesting rant by Linus Torvalds from 20 years ago, arguing that overly strict floating point semantics are of little importance outside scientific domains. Nevertheless, some anecdotes suggest fastmath can cause problems, so it is probably still useful understand what it does and why. If you work in these areas, I would love to hear about your experiences, especially if you identified which of these optimizations had a positive or negative impact.
I hold that in general it’s simply intractable to “defensively” code against the transformations that
ffastmath
may or may not perform. If a sufficiently advanced compiler is indistinguishable from an adversary, then giving the compiler access toffastmath
is gifting that enemy nukes. That doesn’t mean you can’t use it! You just have to test enough to gain confidence that no bombs go off with your compiler on your system.
If you do care about the accuracy of the results, then you need to approach fastmath much more carefully and warily. A common approach is to enable fastmath everywhere, observe erroneous results, and then attempt to isolate and fix the cause as one would usually approach a bug. Unfortunately this task is not so simple: you can't insert branches to check for NaNs or Infs (the compiler will just remove them), you can't rely on a debugger because the bug may disappear in debug builds, and it can even break printing.
So you have to approach fastmath much more carefully. A typical process might be:
Develop reliable validation tests
Develop useful benchmarks
Enable fastmath and compare benchmark results
Selectively enable/disable fastmath optimizations^{[5]} to identify
a. which optimizations have a performance impact,
b. which cause problems, and
c. where in the code those changes arise.
Validate the final numeric results
The aim of this process should be to use the absolute minimum number of fastmath options, in the minimum number of places, while testing to ensure that the places where the optimizations are used remain correct.
Alternatively, you can look into other approaches to achieve the same performance benefits: in some cases it is possible to rewrite the code to achieve the same results: for example, it is not uncommon to see expressions like x * (1/y)
in many scientific codebases.
For SIMD operations, tools such as OpenMP or ISPC provide constructions to write code that is amenable to automatic SIMD optimizations. Julia provides the @simd
macro, though this also has some important caveats on its use. At the more extreme end, you can use SIMD intrinsics: these are commonly used in libraries, often with the help of code generation (FFTW uses this appraoch), but requires considerably more effort and expertise, and can be difficult to port to new platforms.
Finally, if you're writing an open source library, please don't hardcode fastmath into your Makefile.
I think the widespread use of fastmath should be considered a fundamental design failure: by failing to provide programmers with features they need to make the best use of modern hardware, programmers instead resort to enabling an option that is known to be blatantly unsafe.
Firstly, GCC should address the FTZ library issue: the bug has been open for 9 years, but is still marked NEW. At the very least, this behavior should be more clearly documented, and have a specific option to disable it.
Beyond that, there are 2 primary approaches: educate users, and provide finer control over the optimizations.
The easiest way to educate users is to give it a better name. Rather than "fastmath", something like "unsafemath". Documentation could also be improved to educate users on the consequences of these choices (consider this post to be my contribution to toward that goal). Linters and compiler warnings could, for example, warn users that their isnan
checks are now useless, or even just highlight which regions of code have been impacted by the optimizations.
Secondly, languages and compilers need to provide better tools to get the job done. Ideally these behaviors shouldn't be enabled or disabled via a compiler flag, which is a very blunt tool, but specified locally in the code itself, for example
Both GCC and Clang let you enable/disable optimizations on a perfunction basis: these should be standardized to work with all compilers.
There should be options for even finer control, such as a pragma or macro so that users can assert that "under no circumstances should this isnan
check be removed/this arithmetic expression be reassociated".
Conversely, a mechanism to flag certain addition or subtraction operations which the compiler is allowed to reassociate (or contract into a fusedmultiplyadd operation) regardless of compiler flags.^{[6]}
This still leaves open the exact question of what the semantics should be: if you combine a regular +
and a fastmath +
, can they reassociate? What should the scoping rules be, and how should it interact with things like interprocedural optimization? These are hard yet very important questions, but they need to be answered for programmers to be able to make use of these features safely.
For more discussion, see HN.
[1]  Apparently fnomatherrno in GCC can affect malloc , so may not be quite so harmless.

[2]  In fact, it possible to construct array such that taking the sum in different ways can produce almost any floating point value. 
[3]  One important result in numerical analysis is that the error bound on summation is proportional to the sum of the absolute values of the intermediate sums. SIMD summation splits the accumulation over multiple values, so will typically give smaller intermediate sums. 
[4]  A good description of why subnormals incur performance penalties. 
[5]  As mentioned above, fnofinitemathonly should be the first thing you try.

[6]  Rust provides something like this via experimental intrinsics, though I'm not 100% clear on what optimzations are allowed. 