Covered the MISRA loop exits by interposing the shims they test

2026-09-16T14:34:54Z

Under TX_MISRA_ENABLE three kernel loops test a value produced by a function whose whole body returns a constant, so the arm that goes round again cannot execute; the six configurations without the macro compile a plain call, with no loop and no branch at all. Two of the three are the mutex put's prioritize loops and the third is the timer thread's own body. Two new tests define those shim functions themselves. The kernel is built shared and every internal call to either goes through the procedure linkage table, so the executable's definition is the one the kernel reaches and no build file changes. A shim that withholds success on alternate calls sends each mutex loop round exactly twice; the prioritize processing runs unaltered and is idempotent, so the release still leaves the mutex unowned, the suspension list empty and the inherited priority given back, which the test asserts. The timer thread's loop is that thread's whole body, so leaving it ends the thread: that test proves the timer is doing its work first, arms the shim last, and depends on no tick afterwards. Both files record which symbol they replace, why replacing it preserves what surrounds it, and where the replaced function's own coverage comes from -- the other tests, which call both shims through these same constructs. 798/798 in each of the seven configurations. Union coverage is 4383/4383 lines and 3147/3168 branches against 3144 before, the three being one loop exit each; no other outcome moved. Gate raised to 99.25. Assisted-by: Claude Code (Opus 5)

threadx.git/test/tx/regression/threadx_timer_misra_loop_test.c, branch v6.4.1_cert

Covered the MISRA loop exits by interposing the shims they test