[codex] Hoist typed feedback site registration#5295
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughMoves ChangesTyped Feedback Registration Hoist
Benchmark Harness Runner and RSS Updates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
6ca1800 to
8d953ca
Compare
Summary
Hoists typed-feedback site registration out of hot use sites and into function-entry setup. The guard, fallback, pass, and counter calls still run at the original use sites, but the per-site metadata registration now happens once per function entry instead of once per loop iteration.
Also makes the benchmark harness usable on this Linux runner by supporting /usr/bin/time -v RSS output and skipping Node columns when the installed Node cannot execute .ts benchmark inputs directly.
Root cause
benchmarks/suite/10_nested_loops.ts LLVM traces showed js_typed_feedback_register_site(...) inside the hot for.body.21 inner loop before each typed-feedback array guard. That turned static site metadata registration into repeated hot-loop work.
Benchmark Results
Local baseline was captured from e816fc3 because benchmarks/baseline.json is stale for this Linux environment.
Node columns/correctness checks were skipped because local Node cannot run .ts benchmark inputs directly.
Validation
Summary by CodeRabbit
Performance
Documentation
Chores