Covered the retry arms of the two mutex put prioritize loops

2026-09-20T04:58:29Z

Under TX_MISRA_ENABLE the mutex put calls the prioritize processing through a retry loop, so that the call's result is read and the rule about discarding a return value is met. The prioritize processing passes a success status through a shim whose whole body returns success, so the loop's test can only be false on the first pass and the arm that goes round again never ran. The other six configurations compile a plain call with no branch at all. A new test defines the shim itself, which is the technique the monoprocessor suite already uses for the same two loops. The kernel is built shared and every internal reference to the shim goes through the procedure linkage table, so the definition in the test executable is the one reached, with no linker option and no preloading. A shim that withholds success on alternate calls sends each loop round exactly twice and leaves the mutex, the suspension list and the priorities as the kernel expects them. The two loops sit on different paths through a single put, and one release of an inheritance mutex with two suspended waiters reaches both. The shim's reach on this port was measured rather than carried over: objdump gives one call site in the library, in the prioritize processing, because the port overrides the other macro that could expand to it. Read the coverage with that in mind — it is coverage of a kernel whose MISRA shim is the test's, which the file says in its own header. Both sites read two of two in the two MISRA configurations. 123/123 tests pass in each of the eight configurations, and the new test passes fifty standalone repeats in every one of them. Assisted-by: Claude Code (Opus 5)

threadx.git/test/smp/regression/threadx_mutex_misra_prioritize_test.c, branch v6.4.1_cert

Covered the retry arms of the two mutex put prioritize loops