Compiler testing · configuration plans

PlanFuzz

Program behavior depends not only on input but also on packages, routes, backends, and optimizations; conventional fuzzing misses that dimension.

01

Problem

Program behavior depends not only on input but also on packages, routes, backends, and optimizations; conventional fuzzing misses that dimension.

02

Constraints

Flaky executions, infrastructure failures, and preserving the exact mismatch category.

03

Solution

A language-neutral core, typed observations, seven oracle families, fresh-process replay, exact fingerprints, and deterministic program/plan reducers.

04

Outcome

Reproducible artifacts and explicit separation of confirmed, unstable, inconclusive, and infrastructure outcomes.

05

Verification

Fresh-process confirmation, exact fingerprints, typed outcomes, and deterministic reduction.

06

My ownership

Outcome model, oracle core, replay, fingerprinting, and reducers.