diff options
| author | bors <bors@rust-lang.org> | 2022-05-12 02:49:00 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-05-12 02:49:00 +0000 |
| commit | 1d2ea98cff1fde1d8b9e83a0eb639b8ec2cb82d8 (patch) | |
| tree | 5a6932062880a7b698c794abb827ac1f39192948 /compiler/rustc_macros/src | |
| parent | 0cd939e36c0696aad44a213566c9b152f0437020 (diff) | |
| parent | 003b954a43a7f1f9058f25e8f9b6ddfd4a3dced9 (diff) | |
| download | rust-1d2ea98cff1fde1d8b9e83a0eb639b8ec2cb82d8.tar.gz rust-1d2ea98cff1fde1d8b9e83a0eb639b8ec2cb82d8.zip | |
Auto merge of #95837 - scottmcm:ptr-offset-from-unsigned, r=oli-obk
Add `sub_ptr` on pointers (the `usize` version of `offset_from`) We have `add`/`sub` which are the `usize` versions of `offset`, this adds the `usize` equivalent of `offset_from`. Like how `.add(d)` replaced a whole bunch of `.offset(d as isize)`, you can see from the changes here that it's fairly common that code actually knows the order between the pointers and *wants* a `usize`, not an `isize`. As a bonus, this can do `sub nuw`+`udiv exact`, rather than `sub`+`sdiv exact`, which can be optimized slightly better because it doesn't have to worry about negatives. That's why the slice iterators weren't using `offset_from`, though I haven't updated that code in this PR because slices are so perf-critical that I'll do it as its own change. This is an intrinsic, like `offset_from`, so that it can eventually be allowed in CTFE. It also allows checking the extra safety condition -- see the test confirming that CTFE catches it if you pass the pointers in the wrong order.
Diffstat (limited to 'compiler/rustc_macros/src')
0 files changed, 0 insertions, 0 deletions
