C verification reference

On this page

CICD-007: C evidence

CICD-007: C evidence

Class: CORRECTNESS. Obligation: project requirement.

Clang formatting and clang-tidy enforce the configured subset of the C standard. Fixtures must cover accepted and rejected code. Simple one-line branches follow CSTYLE-022; loop bodies keep braces. Review blank-line groups and call/check adjacency where their meaning cannot be inferred by the tools.

The same C job runs Cppcheck and Flawfinder with the shared C analysis policy. Cppcheck findings fail the job; Flawfinder reports risk level 1 and above and fails at level 3. Each analyzer must accept its clean fixture and reject its defect fixture. Executable versions and download digests come from tools/toolchain/lock.toml.

The example checker extracts 24 named files, including nine C translation units, from the three C guides. It runs GCC, Clang, and a Clang sanitizer profile. It does not extract all contextual snippets or the SDD appendix automatically. Negative examples must remain clearly labeled and outside the executable inventory.

The C campaign matrix adds independent engines, resolved include and AST checks. Mock-specific ABI and formal campaigns were removed. The built-in module checker covers a declared subset; LIBMEMALLOC_MODULE_CHECKER remains an override for a qualified external checker. New product sources require profile qualification and do not inherit evidence from the mock.

See build quality and publication for numeric gates, compatibility consumers, compilation metadata and the Pages artifact deployment policy.