rust/tests/ui/consts/offset_from_ub.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:18:27
   |
LL |     let offset = unsafe { ptr_offset_from(field_ptr, base_ptr) };
   |                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called on pointers into different allocations

error[E0080]: evaluation of constant value failed
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
   |
   = note: `ptr_offset_from` called on pointers into different allocations
   |
note: inside `std::ptr::const_ptr::<impl *const u8>::offset_from`
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
note: inside `NOT_PTR`
  --> $DIR/offset_from_ub.rs:24:14
   |
LL |     unsafe { (42 as *const u8).offset_from(&5u8) as usize }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:31:14
   |
LL |     unsafe { ptr_offset_from(field_ptr, base_ptr as *const u16) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ exact_div: 1_isize cannot be divided by 2_isize without remainder

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:44:14
   |
LL |     unsafe { ptr_offset_from(ptr2, ptr1) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called on different pointers without provenance (i.e., without an associated allocation)

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:53:14
   |
LL |     unsafe { ptr_offset_from(end_ptr, start_ptr) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ out-of-bounds `offset_from`: ALLOC0 has size 4, so pointer to 10 bytes starting at offset 0 is out-of-bounds

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:62:14
   |
LL |     unsafe { ptr_offset_from(start_ptr, end_ptr) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ out-of-bounds `offset_from`: ALLOC1 has size 4, so pointer to 10 bytes starting at offset 0 is out-of-bounds

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:79:14
   |
LL |     unsafe { ptr_offset_from_unsigned(field_ptr, base_ptr) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from_unsigned` called on pointers into different allocations

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:86:14
   |
LL |     unsafe { ptr_offset_from(ptr2, ptr1) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called when first pointer is too far ahead of second

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:92:14
   |
LL |     unsafe { ptr_offset_from(ptr1, ptr2) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called when first pointer is too far before second

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:99:14
   |
LL |     unsafe { ptr_offset_from_unsigned(p, p.add(2) ) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from_unsigned` called when first pointer has smaller offset than second: 0 < 8

error[E0080]: evaluation of constant value failed
  --> $DIR/offset_from_ub.rs:106:14
   |
LL |     unsafe { ptr_offset_from_unsigned(ptr2, ptr1) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from_unsigned` called when first pointer is too far ahead of second

error[E0080]: evaluation of constant value failed
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
   |
   = note: `ptr_offset_from` called on different pointers without provenance (i.e., without an associated allocation)
   |
note: inside `std::ptr::const_ptr::<impl *const u8>::offset_from`
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
note: inside `OFFSET_VERY_FAR1`
  --> $DIR/offset_from_ub.rs:115:14
   |
LL |     unsafe { ptr2.offset_from(ptr1) }
   |              ^^^^^^^^^^^^^^^^^^^^^^

error[E0080]: evaluation of constant value failed
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
   |
   = note: `ptr_offset_from` called on different pointers without provenance (i.e., without an associated allocation)
   |
note: inside `std::ptr::const_ptr::<impl *const u8>::offset_from`
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
note: inside `OFFSET_VERY_FAR2`
  --> $DIR/offset_from_ub.rs:121:14
   |
LL |     unsafe { ptr1.offset_from(ptr2.wrapping_offset(1)) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 13 previous errors

For more information about this error, try `rustc --explain E0080`.
bless you 2021-06-18 12:31:56 -05:00			`error[E0080]: evaluation of constant value failed`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`--> $DIR/offset_from_ub.rs:18:27`
Make <*const/mut T>::offset_from `const fn` 2019-08-20 10:51:54 -05:00			`\|`
improve test by using intrinsic directly 2021-06-18 12:43:03 -05:00			`LL \| let offset = unsafe { ptr_offset_from(field_ptr, base_ptr) };`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called on pointers into different allocations
Make <*const/mut T>::offset_from `const fn` 2019-08-20 10:51:54 -05:00
adjust tests 2021-07-12 17:21:35 -05:00			`error[E0080]: evaluation of constant value failed`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
Make <*const/mut T>::offset_from `const fn` 2019-08-20 10:51:54 -05:00			`\|`
Make some diagnostics not depend on the source of what they reference being available 2022-12-09 09:56:23 -06:00			= note: `ptr_offset_from` called on pointers into different allocations
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`\|`
Update std::simd usage and test outputs 2023-11-19 18:04:06 -06:00			note: inside `std::ptr::const_ptr::<impl *const u8>::offset_from`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
			note: inside `NOT_PTR`
			`--> $DIR/offset_from_ub.rs:24:14`
make const_err a future incompat lint 2021-01-30 07:49:22 -06:00			`\|`
adjust tests 2021-07-12 17:21:35 -05:00			`LL \| unsafe { (42 as *const u8).offset_from(&5u8) as usize }`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Make <*const/mut T>::offset_from `const fn` 2019-08-20 10:51:54 -05:00
bless you 2021-06-18 12:31:56 -05:00			`error[E0080]: evaluation of constant value failed`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`--> $DIR/offset_from_ub.rs:31:14`
Make <*const/mut T>::offset_from `const fn` 2019-08-20 10:51:54 -05:00			`\|`
improve test by using intrinsic directly 2021-06-18 12:43:03 -05:00			`LL \| unsafe { ptr_offset_from(field_ptr, base_ptr as *const u16) }`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ exact_div: 1_isize cannot be divided by 2_isize without remainder`
test offset_from with two integers 2019-11-04 06:30:00 -06:00
adjust tests 2021-07-12 17:21:35 -05:00			`error[E0080]: evaluation of constant value failed`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`--> $DIR/offset_from_ub.rs:44:14`
also test different integers 2019-11-04 06:31:29 -06:00			`\|`
adjust tests 2021-07-12 17:21:35 -05:00			`LL \| unsafe { ptr_offset_from(ptr2, ptr1) }`
interpret/miri: better errors on failing offset_from 2024-05-09 06:09:47 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called on different pointers without provenance (i.e., without an associated allocation)
also test different integers 2019-11-04 06:31:29 -06:00
adjust offset_from logic: check that both pointers are in-bounds 2022-03-10 17:30:32 -06:00			`error[E0080]: evaluation of constant value failed`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`--> $DIR/offset_from_ub.rs:53:14`
adjust offset_from logic: check that both pointers are in-bounds 2022-03-10 17:30:32 -06:00			`\|`
			`LL \| unsafe { ptr_offset_from(end_ptr, start_ptr) }`
Normalize alloc-id in tests. 2023-10-15 12:00:11 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ out-of-bounds `offset_from`: ALLOC0 has size 4, so pointer to 10 bytes starting at offset 0 is out-of-bounds
adjust offset_from logic: check that both pointers are in-bounds 2022-03-10 17:30:32 -06:00
			`error[E0080]: evaluation of constant value failed`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`--> $DIR/offset_from_ub.rs:62:14`
adjust offset_from logic: check that both pointers are in-bounds 2022-03-10 17:30:32 -06:00			`\|`
			`LL \| unsafe { ptr_offset_from(start_ptr, end_ptr) }`
Normalize alloc-id in tests. 2023-10-15 12:00:11 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ out-of-bounds `offset_from`: ALLOC1 has size 4, so pointer to 10 bytes starting at offset 0 is out-of-bounds
adjust offset_from logic: check that both pointers are in-bounds 2022-03-10 17:30:32 -06:00
Add `unsigned_offset_from` on pointers Like we have `add`/`sub` which are the `usize` version 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. 2022-04-09 03:27:47 -05:00			`error[E0080]: evaluation of constant value failed`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`--> $DIR/offset_from_ub.rs:79:14`
Add `unsigned_offset_from` on pointers Like we have `add`/`sub` which are the `usize` version 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. 2022-04-09 03:27:47 -05:00			`\|`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`LL \| unsafe { ptr_offset_from_unsigned(field_ptr, base_ptr) }`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from_unsigned` called on pointers into different allocations
Add `unsigned_offset_from` on pointers Like we have `add`/`sub` which are the `usize` version 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. 2022-04-09 03:27:47 -05:00
			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/offset_from_ub.rs:86:14`
			`\|`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`LL \| unsafe { ptr_offset_from(ptr2, ptr1) }`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called when first pointer is too far ahead of second

			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/offset_from_ub.rs:92:14`
			`\|`
			`LL \| unsafe { ptr_offset_from(ptr1, ptr2) }`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from` called when first pointer is too far before second

			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/offset_from_ub.rs:99:14`
			`\|`
Add `unsigned_offset_from` on pointers Like we have `add`/`sub` which are the `usize` version 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. 2022-04-09 03:27:47 -05:00			`LL \| unsafe { ptr_offset_from_unsigned(p, p.add(2) ) }`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from_unsigned` called when first pointer has smaller offset than second: 0 < 8

			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/offset_from_ub.rs:106:14`
			`\|`
			`LL \| unsafe { ptr_offset_from_unsigned(ptr2, ptr1) }`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `ptr_offset_from_unsigned` called when first pointer is too far ahead of second

			`error[E0080]: evaluation of constant value failed`
			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
			`\|`
interpret/miri: better errors on failing offset_from 2024-05-09 06:09:47 -05:00			= note: `ptr_offset_from` called on different pointers without provenance (i.e., without an associated allocation)
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`\|`
Update std::simd usage and test outputs 2023-11-19 18:04:06 -06:00			note: inside `std::ptr::const_ptr::<impl *const u8>::offset_from`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
			note: inside `OFFSET_VERY_FAR1`
			`--> $DIR/offset_from_ub.rs:115:14`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`\|`
			`LL \| unsafe { ptr2.offset_from(ptr1) }`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00
			`error[E0080]: evaluation of constant value failed`
			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
			`\|`
interpret/miri: better errors on failing offset_from 2024-05-09 06:09:47 -05:00			= note: `ptr_offset_from` called on different pointers without provenance (i.e., without an associated allocation)
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`\|`
Update std::simd usage and test outputs 2023-11-19 18:04:06 -06:00			note: inside `std::ptr::const_ptr::<impl *const u8>::offset_from`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
			note: inside `OFFSET_VERY_FAR2`
			`--> $DIR/offset_from_ub.rs:121:14`
interpret, ptr_offset_from: refactor and test too-far-apart check 2022-07-24 15:01:47 -05:00			`\|`
			`LL \| unsafe { ptr1.offset_from(ptr2.wrapping_offset(1)) }`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Add `unsigned_offset_from` on pointers Like we have `add`/`sub` which are the `usize` version 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. 2022-04-09 03:27:47 -05:00
offset, offset_from: allow zero-byte offset on arbitrary pointers 2024-05-09 05:35:11 -05:00			`error: aborting due to 13 previous errors`
Make <*const/mut T>::offset_from `const fn` 2019-08-20 10:51:54 -05:00
bless you 2021-06-18 12:31:56 -05:00			For more information about this error, try `rustc --explain E0080`.