You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8f3d1ef
Browse filesBrowse the repository at this point in the historyBrowse files
JIT: never skip prolog zeroing for untracked GC locals
Instead of extending the safe-point scan with throwing trees, don't mark GC
locals reported as untracked slots as explicitly initialized at all. They
are reported whenever their frame is, and optRemoveRedundantZeroInits runs
before later phases (helper expansion, lowering) that can still introduce
calls, so it can't rule out every gc-safe point before the store. Tracked
GC locals are only reported where they're live and keep the optimization.
Co-authored-by: Copilot App <[email protected]>
Copilot-Session: 45f42362-f012-4030-8643-26f4c1fbf2e1
0 commit comments