-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Rework JIT<->EE communication for struct promotion; add support for general recursive struct promotion #85569
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
Closed
Changes from 4 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
5a69e5c
Rework JIT<->EE communication for struct promotion
jakobbotsch e7bfbbd
Fix a few bugs
jakobbotsch 1d7cde5
SPMI support
jakobbotsch cbba7e0
SSA fix
jakobbotsch 273f432
Retain liberal handling of explicit layout structs with GC pointers
jakobbotsch 35016da
Handle native value types
jakobbotsch bcb95eb
Work around new write barriers after promoting InlineArray
jakobbotsch 3aea901
Promote NFloat, Vector64
jakobbotsch 1756b03
Tweak local morph
jakobbotsch daa4d35
Merge branch 'main' of github.com:dotnet/runtime into fix-85511
jakobbotsch c7833b3
Fix after merge
jakobbotsch cadc3b9
JIT: Allow forward sub to reorder trees throwing same exceptions
jakobbotsch 7e03161
Fix a bug
jakobbotsch 0dd2a89
Add some logging
jakobbotsch 64da446
Run jit-format; clean up a bit
jakobbotsch 3585ed7
Merge branch 'main' of github.com:dotnet/runtime into fix-85511
jakobbotsch dac6e91
Fix after merge
jakobbotsch 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
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
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.
Does this pessimize cases that don't have padding?
Say for example you've defined a
union { float f; int32_t i; }and therefore it is explicit, but the two structures are "perfectly overlapping".-- JW as a potential "future" improvement, not something to be handled in this PR or anything
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.
No, since we don't support promotion of structs with overlapping fields. But if we did still no as the JIT only pays attention to
significantPaddingwhen there are holes in the struct.