Skip to content

Draft diagnostic: isolate Flash magma memory regression with five-flag ablation - #126

Draft
heathsanchez wants to merge 3 commits into
flashfrom
research/flash-magma-flag-causal-20261104
Draft

heathsanchez wants to merge 3 commits into
flashfrom
research/flash-magma-flag-causal-20261104

Conversation

@heathsanchez

Copy link
Copy Markdown
Collaborator

Causal hypothesis only — do not merge

The published attributed Flash build (78c7502bac8a5ba000057b3f083bc0595ac65750) has one known false REJECT: official Arena valid perf/magma-list-pair-n21 (published report ~14.6 GB RSS). Upstream sokonanoda accepts this exact source at ~7.6 GB.

This isolated diagnostic disables five published Flash flags together (DIRECT_VAR_EVAL, DIRECT_FRAMED_PRUNE, INFER_PI_DEMAND_BYPASS, RIGID_INDUCTIVE_NEUTRAL, APP_HC_PREALLOC) without modifying the algorithmic code. The official archive and n21 fixture have exact source hashes. Two binaries compile from exact source, with identical release settings and 2 threads; paired n7/n21 acceptance, wall, CPU and peak RSS are preserved, including failures.

Interpretation: If the all-off version accepts n21 with lower memory while published fails, bisect these switches next. If both fail, the switches are not sufficient. If both accept, resource nonreproducibility remains. No combined correctness proof, no nonregression, and no valid grounds for Arena submission.

Follow-up only after a meaningful delta: isolate the responsible switch, keep full protected 179 cases + extra performance tests, then match full Mathlib. This draft does not include the six soundness repairs in PR #125.

Upstream source attribution preserved; no private internal research notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant