FP32 FFMA (CUDA cores)

Scalar FP32 fused multiply-add on the CUDA cores, which is the path the unlock never governed.

How this path is measured

Register-resident fma.rn.f32 issue rate: eight independent accumulator chains per warp, best of three timed runs. Library SGEMM rows are grouped with the other cuBLAS GEMMs instead, because a fixed M.N.K call and an issue loop are not the same measurement.

Governed by the SM speed-select fuse: no

What the unlock changes on this path

8 rows over 8 cards. 0 improved by more than 5%, 8 did not; the largest gain is GeForce RTX 3050 6GB at 1.01×.

ModeStockUnlockedGainCard
ffma · FP32 was never rate-limited8.408.50 TF/s1.01×GeForce RTX 3050 6GB · GA107 · 18 SMs
ffma · FP32 was never rate-limited49.449.7 TF/s1.01×GeForce RTX 4080 SUPER · AD103 · 80 SMs
ffma · FP32 was never rate-limited36.636.7 TF/s1.00×GeForce RTX 4070 SUPER · AD104 · 56 SMs
ffma · FP32 was never rate-limited40.140.2 TF/s1.00×GeForce RTX 4070 Ti · AD104 · 60 SMs
ffma · FP32 was never rate-limited79.179.1 TF/s1.00×GeForce RTX 4090 · AD102 · 128 SMs
ffma · FP32 was never rate-limited31.731.7 TF/s1.00×GeForce RTX 4070 (AD103) · AD103 · 46 SMs
ffma · FP32 was never rate-limited32.132.1 TF/s1.00×GeForce RTX 4070 (Gigabyte) · AD104 · 46 SMs
ffma · FP32 was never rate-limited50.850.7 TF/s1.00×GeForce RTX 4080 · AD103 · 76 SMs

The smallest ratio in this set is GeForce RTX 4080 at 1.00×.

Reading the numbers

A 1.00× row is not a failed unlock. It says that particular path was never rate-limited, so the override had nothing to restore. If you benchmark your own card and see 1.00× on the mode you care about, the unlock may well have applied correctly and simply does not help that workload.

Other measurement paths