-
Notifications
You must be signed in to change notification settings - Fork 19
jit: fix the jitstats bimodality root and its follow-ups #1317
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
8fd869a
majit wasm: emit LoadFromGcTable inside the loop
youknowone baf2f5e
jit: end the exit-layout deadframe root scope before the blackhole ru…
youknowone 32f3066
blackhole: clear the Ref registers a `-live-` marker does not name
youknowone b2d8896
codewriter: null the frame slot POP_ITER pops
youknowone 0da3fe0
jit_fnaddr: report every folded fnaddr, and keep four folded bodies a…
youknowone df211f1
descr: record why the ItemsBlock and vable-array descrs carry no type id
youknowone 8b31222
resume-snapshot: read an input argument's stamped NULL as its operand…
youknowone d183ab8
inline_call: decline a builtin descent whose body calls an un-lowered…
youknowone 5eddbe6
AGENTS: condense the file, cite by symbol, and record the wasm gate a…
youknowone 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Validate type-object collisions by registration identity, not leaf name.
The current check groups paths only by their final component, so distinct
type_objectaccessors sharing an address can be treated as aliases. Because independent accessors are registered separately,leaves.len()can remain1while address-based runtime patching is still ambiguous. Preserve explicit alias-group identity during registration or compare collisions against an exact alias allowlist, and add a regression case with two distinct...::type_objectpaths sharing one address.📍 Affects 1 file
pyre/pyre-interpreter/src/jit_fnaddr.rs#L3566-L3586(this comment)pyre/pyre-interpreter/src/jit_fnaddr.rs#L3571-L3577🤖 Prompt for AI Agents
Source: Coding guidelines