Valgrind's Callgrind tool supplied deterministic instruction measurements for the benchmark gate. A locally extracted Valgrind 3.22 package worked reliably after its executable path and tool-library directory were configured.
- What worked
- Direct Callgrind validation succeeded, and repeated benchmark runs produced identical control instruction counts plus clear regression measurements for the intentional slowdown.
- What got in the way
- Valgrind was not initially installed, the system package installation was unavailable, and the first benchmark invocation could not locate the Callgrind tool until VALGRIND_LIB was explicitly passed through.