-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Add a special case for align_offset /w stride != 1 #98866
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
// assembly-output: emit-asm | ||
// compile-flags: -Copt-level=1 | ||
// only-x86_64 | ||
// min-llvm-version: 14.0 | ||
#![crate_type="rlib"] | ||
|
||
// CHECK-LABEL: align_offset_byte_ptr | ||
// CHECK: leaq 31 | ||
// CHECK: andq $-32 | ||
// CHECK: subq | ||
#[no_mangle] | ||
pub fn align_offset_byte_ptr(ptr: *const u8) -> usize { | ||
ptr.align_offset(32) | ||
} | ||
|
||
// CHECK-LABEL: align_offset_byte_slice | ||
// CHECK: leaq 31 | ||
// CHECK: andq $-32 | ||
// CHECK: subq | ||
#[no_mangle] | ||
pub fn align_offset_byte_slice(slice: &[u8]) -> usize { | ||
slice.as_ptr().align_offset(32) | ||
} | ||
|
||
// CHECK-LABEL: align_offset_word_ptr | ||
// CHECK: leaq 31 | ||
// CHECK: andq $-32 | ||
// CHECK: subq | ||
// CHECK: shrq | ||
// This `ptr` is not known to be aligned, so it is required to check if it is at all possible to | ||
// align. LLVM applies a simple mask. | ||
// CHECK: orq | ||
#[no_mangle] | ||
pub fn align_offset_word_ptr(ptr: *const u32) -> usize { | ||
ptr.align_offset(32) | ||
} | ||
|
||
// CHECK-LABEL: align_offset_word_slice | ||
// CHECK: leaq 31 | ||
// CHECK: andq $-32 | ||
// CHECK: subq | ||
// CHECK: shrq | ||
// `slice` is known to be aligned, so `!0` is not possible as a return | ||
// CHECK-NOT: orq | ||
#[no_mangle] | ||
pub fn align_offset_word_slice(slice: &[u32]) -> usize { | ||
slice.as_ptr().align_offset(32) | ||
} |
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.
Thinking about it again, there may be a better way to compute the element offset in the first place rather than dividing the byte offset. I believe this won’t regress
stride == 1
case anyway and this division won’t actually appear in most of the code that immediately passes the result from this function to anoffset
, either so I wouldn’t consider it a blocker for the time being.