-
Notifications
You must be signed in to change notification settings - Fork 5.5k
JIT: Tail-merge process all sets at once #129363
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
Open
BoyBaykiller
wants to merge
8
commits into
dotnet:main
Choose a base branch
from
BoyBaykiller:tail-merge-process-sets-at-once
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+117
−123
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
c77a8f2
* process all sets at once
BoyBaykiller a8dc6bc
* fix error C4018: '>': signed/unsigned mismatch
BoyBaykiller 5753921
* use custom jitstd::partition
BoyBaykiller 56139e4
* dont use std::distance
BoyBaykiller 91edc35
* try fix x86 tp
BoyBaykiller 534ebff
* fix 'const' position
BoyBaykiller 42a53d7
* use custom partition again
BoyBaykiller 92a8a5f
Merge branch 'main' of https://github.com/dotnet/runtime into tail-me…
BoyBaykiller 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
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.
Behavior change worth confirming: in the cross-jump path the retry is now scheduled only when
hasCommSucc, so the return/throw dedup pass (commSucc == nullptr) no longer re-visitscrossJumpTarget. The old code always pushedcrossJumpTargetontoretryBlocksand, together with the previousdo { ... } while (tailMergePreds(nullptr))loop, iterated the return/throw merge until fixpoint. With the single-passpartitionapproach a splitcrossJumpTargetthat gains a new matching last statement is no longer reconsidered against the remaining return/throw blocks. If SPMI asmdiffs show this is intentional/neutral, please note it; otherwise this may be a small optimization regression relative to the prior iterative behavior.