-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Fix ABI for Int128 #73601
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
Fix ABI for Int128 #73601
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
9024f6c
Add ABI tests for Int128 covering interesting scenarios
davidwrighton 74935a1
New test
davidwrighton be730bc
Fix auto layout algorithm to compute structure alignment correctly
davidwrighton e599574
Re-enable disabled test
davidwrighton 3ef8ee4
Remove file that shouldn't be added as part of the new test
davidwrighton 0cdf40b
Make a few test types public to silence unassigned field errors
trylek ebb920c
Merge branch 'fix_65281' of github.com:davidwrighton/runtime into fix…
davidwrighton 174590f
Update comments and add more testing
davidwrighton fe87927
Merge branch 'main' of github.com:dotnet/runtime into fix_72206
davidwrighton ffda43d
First stab at support for proper 128bit integer layout and abi
davidwrighton dbc3c0b
Merge branch 'fix_72206' of github.com:davidwrighton/runtime into fix…
davidwrighton d675132
Fix bugs so that at least Windows Arm64 works
davidwrighton 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Maybe use
int8_tto better validate 32bit platforms that expect 4 byte alignment instead of 8/16 ones?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.
it doesn't matter too much. The way alignment works in the various architectures we support/are likely to support, there won't be a meaningful difference. However, this is altogether messy enough that we may simply remove the ability to pass Int128 across the p/invoke boundary.
Uh oh!
There was an error while loading. Please reload this page.
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.
Noting that while blocking this is fine for .NET 7 given the short timeframe and that its currently busted. This won't be viable longer term.
Int128is an ABI primitive and much likeVector128<T>needs to eventually be supported.