kavak.run compiler stack

Conformance · measured, not claimed

How much Objective-C actually runs.

Objective-C has no official compiler suite, so the measurement is a curated ledger.

82.6%223 of 270 in-scope ledger rows
  • passing223
  • not yet supported47
  • wrong — a real defect0
  • out of scope / no arbiter0
What was measured
Authority
languages/ObjectiveC/tests/corpus/manifest.tsv
Arbiter
macOS clang (-fobjc-arc -fblocks), row by row in the oracle column; a row where clang does not compile or prints something else is self (our own recorded output)
Unit
ledger row
Measured
2026-10-07 03:25

breakdown

Breakdown by corpus area

corpus areatestspassingnot yetwrongout of scopepass ratesplit
generated139139000100.0%
probe11063470057.3%
corpus2121000100.0%

blockers

What blocks the rest

The ten most expensive blockers. Next to each is how many ledger rows it costs — one compiler gap can stop a whole file, so the cost is what matters, not the count of distinct errors.

costreason — the measurement's own wordsblamed
1undeclaredprobe/r001_undeclared.m
1undeclared classprobe/r002_undeclared_class.m
1conflictprobe/r003_conflict.m
1void paramprobe/r006_void_param.m
1not implementedprobe/r007_not_implemented.m
1reservedprobe/r008_reserved.m
1too longprobe/r009_too_long.m
1extra argprobe/r011_extra_arg.m
1const tokenprobe/r013_const_token.m
1alloc overrideprobe/r014_alloc_override.m

A further 37 ledger rows are blocked by smaller causes; the full list is in the raw measurement (JSON).