|
Some checks are pending
CI Benchmark - Fusion Loop Timing / Fusion Loop Timing Benchmark (push) Waiting to run
Add a comment next to the per-test setjmp(g_test_jmp) guard in main()'s loop recording the C11 7.13.2.1 volatile analysis: the loop index i is read in the post-longjmp path (g_tests[i].name) but is not modified between the setjmp() call and a possible longjmp() — the body only reads i, and the only write is the for-loop increment, which runs after control returns. So no volatile qualifier is needed. (bf-2ftl) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile | ||
| test_runner.c | ||
| test_runner.h | ||
| test_sanity.c | ||