Auto merge of #2352 - saethlin:new-benchmark, r=RalfJung

Add a benchmark of the hang-on-test-failure code path

This is the code pattern that produces the performance problem in https://github.com/rust-lang/miri/issues/2273

I figured out what I was stuck on in https://github.com/rust-lang/miri/pull/2315#discussion_r916387919. For a while I was just doing `let x: &[u8] = &[0u8; 4096];` but that doesn't produce the runtime inside `Stack::item_popped` that I was looking for, I think because this allocation is never deallocated. But with `Vec`, I get the profile I'm looking for.

bench-cargo-miri/slice-get-unchecked/Cargo.lock

@@ -0,0 +1,7 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 3
+
+[[package]]
+name = "slice-get-unchecked"
+version = "0.1.0"

bench-cargo-miri/slice-get-unchecked/Cargo.toml

@@ -0,0 +1,8 @@
+[package]
+name = "slice-get-unchecked"
+version = "0.1.0"
+edition = "2021"
+
+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
+
+[dependencies]

bench-cargo-miri/slice-get-unchecked/src/main.rs

@@ -0,0 +1,12 @@
+//! This is a stripped-down version of the code pattern that causes runtime blowup when printing
+//! backtraces in a failed test under cargo miri test with -Zmiri-disable-isolation.
+//! See https://github.com/rust-lang/miri/issues/2273
+
+fn main() {
+    let x = vec![0u8; 4096];
+    let mut i = 0;
+    while i < x.len() {
+        let _element = unsafe { *x.get_unchecked(i) };
+        i += 1;
+    }
+}