Closes #3448 var x : [4]GF16; -> GF16 x[4]; error: use of undeclared identifier 'GF16' The same element is `uint16_t` in a parameter (`uint16_t a[static 4]`) and in a struct field (`uint16_t f[4];`). Only the local path passed the t27 text through, because it gated on `is_primitive` -- and the note retiring that very gate sits two hundred lines below, on `param_type_to_c`: W583: this used to be gated on `is_primitive`, which lists only the integer scalars -- so `f32`, `f64`, `str`, `string` and `gf16` took the pass-through arm and reached C unmapped even after `type_to_c` learned them. Same sentence, same file, other position. Two more defects live in the same eight lines. `var x : []u8;` emitted `uint8_t x[];`, which is not a definition; and `var x : []const u8;` emitted `const u8* x`, because the qualifier lives INSIDE the element text and this path did not strip it. The first slice repair was wrong, and the corpus said so: rewriting every `[]T` local to a pointer broke `T x[] = { ... }`, which is legal C and takes its size from the initialiser list. +5 errors, nothing better, in the one file carrying the shape. `size.is_empty() && node.children.is_empty()` is that measurement kept as code. MEASURED, and this is the part that matters beyond this commit. CLANG'S DEFAULT -ferror-limit=20 HAS BEEN CENSORING EVERY TOTAL I HAVE PUBLISHED THIS SESSION. 141 files reach the limit. The corpus emits 15133 errors, not the 3849 reported. The per-file splits were sound, because they were counted per file; the totals were floors. this change 15133 -> 15126 3 files better, 0 worse #3447, re-measured 15188 -> 15133 published as 3849 -> 3825 The direction and the per-file conclusions stand; the magnitudes were understated. It surfaced because a repair that removes real errors showed a ZERO delta -- three files sitting at exactly 20 before and after. tools/backend_parity_table.py gains the fourth position. Its first probe there measured the wrong thing: `var x : T;` with no initialiser is declared by C and Rust and emitted by NEITHER Zig nor Verilog, so the table was reading their dead-code removal. Initialising from a parameter of the same type fixed it, and the self-check now covers all four positions. Four mutants, four dead. 14 seals refreshed in the same commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Commits

Commits on Sep 8, 2026

gen-c: lower the element type of a local array