-
Notifications
You must be signed in to change notification settings - Fork 14k
Replace OffsetOf by an actual sum of calls to intrinsic. #148151
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
base: main
Are you sure you want to change the base?
Conversation
0dc894f to
e46804b
Compare
This comment has been minimized.
This comment has been minimized.
e46804b to
8f24a32
Compare
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Replace OffsetOf by an actual sum of calls to intrinsic.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (7721497): comparison URL. Overall result: ❌✅ regressions and improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -1.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 473.876s -> 473.729s (-0.03%) |
|
☔ The latest upstream changes (presumably #148324) made this pull request unmergeable. Please resolve the merge conflicts. |
875c6f6 to
9fd16d6
Compare
|
Some changes occurred in match checking cc @Nadrieril Some changes occurred to the CTFE machinery
cc @rust-lang/wg-const-eval Some changes occurred to constck cc @fee1-dead Some changes occurred in src/tools/clippy cc @rust-lang/clippy This PR changes rustc_public cc @oli-obk, @celinval, @ouz-a Some changes occurred in cc @BoxyUwU Some changes occurred to the intrinsics. Make sure the CTFE / Miri interpreter cc @rust-lang/miri, @RalfJung, @oli-obk, @lcnr This PR changes MIR cc @oli-obk, @RalfJung, @JakobDegen, @vakaras Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 Some changes occurred to the CTFE / Miri interpreter cc @rust-lang/miri Some changes occurred in compiler/rustc_codegen_ssa This PR changes a file inside |
|
What's the justification/benefit for doing this, and what user facing impact does it have (i.e. why does it need a lang nomination)? |
|
My justification is simplifying MIR. This feature was implemented as a specific MIR statement, but does not need to, an intrinsic is sufficient. There should be no user-facing change because of the However, there are 2 user-facing changes in this PR that t-lang may want to know:
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
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.
rustc_const_eval changes LGTM.
| let tp_ty = instance.args.type_at(0); | ||
|
|
||
| let u32_layout = self.layout_of(self.tcx.types.u32)?; | ||
| let variant = self.read_scalar(&args[0])?.to_bits(u32_layout.size)? as u32; |
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.
| let variant = self.read_scalar(&args[0])?.to_bits(u32_layout.size)? as u32; | |
| let variant = self.read_scalar(&args[0])?.to_u32()?; |
|
|
||
| let u32_layout = self.layout_of(self.tcx.types.u32)?; | ||
| let variant = self.read_scalar(&args[0])?.to_bits(u32_layout.size)? as u32; | ||
| let field = self.read_scalar(&args[1])?.to_bits(u32_layout.size)? as usize; |
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.
| let field = self.read_scalar(&args[1])?.to_bits(u32_layout.size)? as usize; | |
| let field = self.read_scalar(&args[1])?.to_u32()? as usize; |
| /// Therefore, implementations must not require the user to uphold | ||
| /// any safety invariants. | ||
| /// | ||
| /// The stabilized version of this intrinsic is [`core::mem::offset_of`]. |
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.
This can also only be called at compile time, right? Please add that note to the comment.
Also, would be good to explain why this is a lang item, since that is very unusual for intrinsics.
|
☔ The latest upstream changes (presumably #148721) made this pull request unmergeable. Please resolve the merge conflicts. |
4699a81 to
d65ccdd
Compare
This comment has been minimized.
This comment has been minimized.
|
☔ The latest upstream changes (presumably #148658) made this pull request unmergeable. Please resolve the merge conflicts. |
|
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
| // CHECK: concrete::[[const_z0]]: usize | ||
| // CHECK: [[z:_.*]] = offset_of::<Alpha>(const 0_u32, const 2_u32) | ||
| // CHECK: [[z0:_.*]] = offset_of::<Beta>(const 0_u32, const 0_u32) | ||
| // CHECK: [[sum:_.*]] = AddWithOverflow(copy [[z]], copy [[z0]]); |
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.
pondering: Can this ever overflow? Wouldn't the type have to be malformed for it to happen? Since we're only ever running it in CTFE, could it be AddUnchecked instead, and if it ever does overflow it'll get trapped by the UB-in-CTFE checks?
(Aside: appreciate the test here -- I came looking for it as soon as I was reading the code in mir_build.)
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.
Actually, I'm kinda confused how it's AddWithOverflow here -- at https://github.com/rust-lang/rust/pull/148151/files#diff-ad5988b23007e07f23d5459907b7aa75c9dc6ae82623be8cd4bc6acc58cb3397R863 it's BinOp::Add, not BinOp::AddWithOverflow.
Is there a TerminatorKind::Assert in here too somehow?
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 cannot possibly overflow, but as I made the transform happen on THIR, removing the overflow checks would only make stuff more complex.
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.
I added a THIR-print test to show what the generated THIR looks like.
| #[rustc_intrinsic_const_stable_indirect] | ||
| #[rustc_intrinsic] | ||
| #[lang = "offset_of"] | ||
| pub const fn offset_of<T: PointeeSized>(variant: u32, field: u32) -> usize; |
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.
Musing: Is there ever a need to pass values into this? Why is it phrased this way as opposed to, say
| pub const fn offset_of<T: PointeeSized>(variant: u32, field: u32) -> usize; | |
| pub const fn offset_of<T: PointeeSized, const Variant: u32, const Field: u32>() -> usize; |
(Not that the way it is is bad -- I think it's fine -- just came to mind as I was reading through stuff.)
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.
r=me with the trivial comment fix. I left a bunch of other things on the way by that you can think about as well, but I don't think any of them are critical.
d65ccdd to
d78c14e
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
d78c14e to
fc6c34f
Compare
|
☔ The latest upstream changes (presumably #148957) made this pull request unmergeable. Please resolve the merge conflicts. |
fc6c34f to
5b48fd9
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
5b48fd9 to
85eca56
Compare
This PR changes the way we compute the value of the
offset_of!macro in MIR. The current implementation uses a dedicated MIR rvalue.This PR proposes to replace it by an inline constant which sums calls to a new intrinsic
offset_of(variant index, field index). The desugaring is done at THIR building time, easier that doing it on MIR.The new intrinsic is only meant to be used by const-eval. LLVM codegen will refuse to generate code for it.
We replace:
By:
The second commit modifies intrinsic const checking to take
allow_internal_unstableinto account. The new intrinsic should only be called from stableoffset_of!macro. The intrinsic itself is unstable, const-unstable, butrustc_intrinsic_const_stable_indirect.Fixes #123959
Fixes #125680
Fixes #129425
Fixes #136175
r? @ghost