Skip to content

Draft diagnostic: reproduce official Arena PGO build on magma false REJECT - #127

Draft
heathsanchez wants to merge 3 commits into
flashfrom
research/flash-pgo-arena-repro-20261104
Draft

heathsanchez wants to merge 3 commits into
flashfrom
research/flash-pgo-arena-repro-20261104

Conversation

@heathsanchez

Copy link
Copy Markdown
Collaborator

Arena build-fidelity diagnostic (draft only)

The official MathGraph checker declaration specifies a three-stage profile-guided build that earlier local regression runs did not reproduce: -Cprofile-generate, training on official init-prelude, llvm-profdata merge, and -Cprofile-use (all with -C target-cpu=native). Its runtime uses num_threads:2.

This experiment uses exact published source commit 78c7502bac8a5ba000057b3f083bc0595ac65750; no src/ changes. It compiles an ordinary matched release and an Arena-style PGO binary on one runner, pins the official test tar SHA and the exact perf/magma-list-pair-n21 source SHA, then compares n7 and n21 verdicts, wall, CPU and RSS while preserving profile and negative evidence.

Why: official public Arena currently records an unexpected REJECT on valid n21 with ~14.6 GB RSS, while a plain release compiled on a GitHub runner accepted the identical input with ~12.7 GB RSS (run #41745436392). An all-fast-paths-off variant was slower and used more memory there, so the flags were not sufficient to explain the discrepancy.

Boundaries: exact build procedure tested but not necessarily the same Arena CPU, Nix toolchain or hardware. No change to Arena release, no soundness or speed claim beyond the measured gate. If the PGO binary reproduces the failure, follow with exact-source PGO candidate of six-guard PR #125 and a source-pinned memory causal tournament.

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