@run:0 miri: @revisions: stack tree miri: @[tree]compile-flags: -Zmiri-tree-borrows Test what happens when we read parts of a pointer. Related to <htt

Ensure that we can move between allocations after casting back to a ptr

Ensure we can cast back a different integer than the one we got when exposing.

Ensure that we can roundtrip through a pointer with an address of 0

Ensure we can expose the address of a pointer that is out-of-bounds

Make sure that reading from an `&mut` does, like reborrowing to `&`, NOT invalidate other reborrows.

Same as above, but this time we first create a raw, then read from `&mut` and then freeze from the raw.

Checks that accessing a reborrowed wildcard reference doesn't invalidate other reborrowed wildcard references, if they are also exposed.

Updates `self` to account for a foreign access.

Records a new access, so that future access can potentially be skipped by `skip_if_known_noop`. This must be called on child accesses, and otherwise s

Adding a protector for `Ref` would break this

Just to make sure that casting a ref to raw, to int and back to raw and only then using it works. This rules out ideas like "do escape-to-raw lazily";

Pretend that the reference has interior mutability. Don't actually mutate it though, it will fail because it has a Frozen parent.

Knowing the relative position of `x` to `y`, determine the relative position of the accessed pointer defined by `self` relative to each `x` and `y`.

Traverses the entire tree looking for useless tags. Removes from the tree all useless child nodes of root. It will not delete the root itself. NOTE:

Like [`Self::remove_useless_children`], but takes a slice of *dead* tags to remove instead of a set of *live* tags to keep. See [`AllocState::remove_d

This makes a ref that was passed to us via &mut alias with things it should not alias with

This checks that a reborrowed mutable reference returned from a function is actually writeable. The fact that this is not obvious is due to the additi

Analogous to same test in `../tree-borrows.rs` but with returning a reborrowed wildcard reference.

Analogous to same test in `../tree-borrows.rs` but with a protected wildcard reference.

Time a single Miri test, excluding `cargo-miri` overhead, by capturing its final `miri` invocation as a standalone script.

Make sure we do not have bad enum layout optimizations.

The test taken from the Rust documentation.

Performs the setup required to make `cargo bsan` work: Getting a custom-built libstd. Then sets `BSAN_SYSROOT`. Skipped if `BSAN_SYSROOT` is already s

This is not a data race!

Example that should be UB but due to wildcard pointers being too permissive we don't notice.

Make sure that creating a *mut does not invalidate existing shared references.

The test taken from the Rust documentation.