a * b + c looks like two operations, and in plain IEEE arithmetic it is: multiply, round to the nearest double, add, round again. Most modern CPUs and GPUs also have a fused multiply-add that computes the product exactly and rounds only once at the end. That is fma(a, b, c) in C's <math.h>.
Two consequences.
It can be more accurate. The exact error of a product, which normally you cannot get, becomes cheap:
#include <math.h>
double p = a * b; /* rounded product */
double err = fma(a, b, -p); /* exact: a*b == p + err */
Since the true product is p + err exactly (barring overflow and underflow), the pair is a "double-double" building block, used in compensated summation and dot products.
It makes results differ between machines. If the compiler is allowed to contract a * b + c into a fused operation, the same source gives different low-order bits depending on target and flags. GCC may do it by default in its GNU dialects when the hardware has the instruction; -ffp-contract=off turns it off. In C there is also the FP_CONTRACT pragma. On GPUs, shader compilers often fuse by default for speed.
So when a test compares floats bit for bit between a CPU run and a GPU run, a mismatch is not necessarily a bug. It may just be one rounding instead of two. Tolerances in the last few ulps are the honest approach.