Posts, notes, and experiments.
Technical Retrospective: Stabilizing REX's Clang Frontend CTest Suite
A technical retrospective on the REX Clang frontend stabilization PR: major failure families, root causes, key changed subsystems, and the risks that remain after the full CTest suite went green.
Read more ⟶How REX Cleaned Up A Thousand Historical Test Failures Without Bounce
How a twelve-day REX cleanup used Codex, GPT-5.5, and a strict no-bounce repair loop to move roughly one thousand historical CTest failures to a full-suite green result.
Read more ⟶How REX Fixed the Cxx_Grammar Timeout by Owning the Frontend Traversal Boundary
A case study from the REX Clang frontend migration: why the generated Cxx_Grammar translation test timed out, how the failure exposed an over-eager header traversal policy, and how the fix avoided unparser hacks and CTest masking.
Read more ⟶What Changed When REX Was Re-Evaluated Against LLVM 22
The final REX OpenMP Journey post: what happened when the optimized REX GPU suite was rebuilt against source-built LLVM 22, which margins moved, and why no new correctness or performance regression was confirmed.
Read more ⟶How REX Finished The LLVM 21 GPU Benchmark Suite
The final LLVM 21 REX GPU performance wrap-up: why REX wins or ties every benchmark in the fair suite, which compiler mechanisms explain each result, and what native LLVM still does better even when it loses.
Read more ⟶How REX Removed Process-Exit Offload Teardown From Generated GPU Programs
The next REX GPU performance post: how srad_v2 niter=0 exposed a fixed process-lifecycle tax, why explicit offload teardown at process exit was unnecessary for short-lived generated programs, and how REX kept rex_offload_fini as an explicit API without forcing it into every main.
Read more ⟶How REX Separated GPU-Total From Wall-Clock Noise In pathfinder And srad
The next REX GPU performance post: why pathfinder and srad looked like remaining regressions under wall-clock timing, how nvprof GPU-total measurements changed the conclusion, and why the right fix was methodology discipline rather than another compiler heuristic.
Read more ⟶How REX Recovered b+tree Read-Only Loads With __ldg
The next REX GPU performance post: how the remaining fair b+tree gap moved from launch geometry into read-only memory access, why a global cache flag was the wrong fix, and how REX repaired const provenance so generated kernels could recover __ldg loads safely.
Read more ⟶How REX Kept b+tree Launch Geometry Fair
The next REX GPU performance post: how b+tree exposed a real launch-geometry problem, why shrinking explicit user launch clauses would be an unfair benchmark win, and how REX turned the experiment into a generic default-only heuristic.
Read more ⟶How REX Completed Direct __tgt_target_kernel Lowering And Repaired The Device ABI
The next REX GPU performance post: why switching from legacy __tgt_target_teams to direct __tgt_target_kernel was a full host/device ABI migration, how gaussian exposed the mismatch, and how REX repaired the generated kernel signature, scalar transport slots, and runtime argument packet.
Read more ⟶