Diag
Find which buffer is the precision sink — without source instrumentation.
What it will do
Diag attaches to a GDB or LLDB session and lets you
dump float buffers from the float build,
overwrite the matching buffers in the fixed build,
regenerate the output .wav, and binary-search across
buffers to find which one introduces the precision loss.
Why no instrumentation
All buffer access happens through the debugger — there are no
printfs, no recompiles, and no source-tree changes.
The fixed build under test stays bit-identical to the one your
pipeline ships.
Diag is on the roadmap. The Wave Compare and Debugger modes already cover most of the same workflow today.