-
-
Notifications
You must be signed in to change notification settings - Fork 158
fix(codegen): retry oversized RS4GC functions with shadow roots (#8679) #8687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
proggeramlug
wants to merge
1
commit into
PerryTS:main
from
proggeramlug:fix/8679-rs4gc-budget-spill-retry
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Fixed large native functions whose statepoint rewrite crossed the LLVM | ||
| instruction budget but fell below the root-spill estimate threshold. Perry now | ||
| re-lowers only those functions with precise shadow-frame roots and retries the | ||
| same optimization pipeline instead of refusing the whole codegen unit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win
Order the late frame push before the retained
js_shadow_slot_bindcalls.emit_shadow_frame_pushappends to the selected region. On the late-spill path the region is already populated. Whenshadow_frame_post_init_regionis true,entry_setup_call_voidhas already pushed everyjs_shadow_slot_bindline intoentry_post_init_setup, so appending the push there renders:The binds then write into the caller's frame, not this function's. The GC root map for the function is wrong for every slot, which can free a live object. The early (estimate-driven) path does not have this problem because
reserve_shadow_slotcreates the push before the first bind is emitted.crates/perry-codegen/src/function.rsline 1429 only asserts that the three calls are present, so the existing test passes with the wrong order. Add an order assertion on@js_shadow_frame_enterbefore@js_shadow_slot_bind.🐛 Proposed fix: splice the push at the region start on a late request
Then call it from
request_shadow_frame_spillwithSome(0):Note:
alloca_entryinsideemit_shadow_frame_pushstill appends the handle/state slots toentry_allocas, which is correct becauseentry_allocasis spliced at the top of block 0.📝 Committable suggestion
🤖 Prompt for AI Agents