rust/tests/mir-opt/slice_drop_shim.rs

// skip-filecheck
//@ compile-flags: -Zmir-opt-level=0 -Clink-dead-code
// mir-opt tests are always built as rlibs so that they seamlessly cross-compile,
// so this test only produces MIR for the drop_in_place we're looking for
// if we use -Clink-dead-code.

// EMIT_MIR core.ptr-drop_in_place.[String].AddMovesForPackedDrops.before.mir
fn main() {
    let _fn = std::ptr::drop_in_place::<[String]> as unsafe fn(_);
}
Allow to run filecheck in mir-opt tests. 2023-10-17 01:36:39 +08:00			`// skip-filecheck`
Tweak a few mir-opt tests instead of using -Clink-dead-code 2024-01-31 11:28:28 +08:00			`//@ compile-flags: -Zmir-opt-level=0 -Clink-dead-code`
			`// mir-opt tests are always built as rlibs so that they seamlessly cross-compile,`
			`// so this test only produces MIR for the drop_in_place we're looking for`
			`// if we use -Clink-dead-code.`
Remove unnecessary `EMIT_MIR_FOR_EACH_BITWIDTH 2022-09-05 13:35:47 +08:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 15:40:56 +08:00			`// EMIT_MIR core.ptr-drop_in_place.[String].AddMovesForPackedDrops.before.mir`
Add test for slice drop shims 2019-03-31 01:18:54 +08:00			`fn main() {`
Improve SimplifyLocals pass so it can remove unused consts The `ConstProp` can cause many locals to be initialized to a constant value and then never read from. `ConstProp` can also evaluate ZSTs into constant values. Previously, many of these would be removed by other parts of the MIR optimization pipeline. However, evaluating ZSTs (especially `()`) into constant values defeated those parts of the optimizer and so in a2e3ed5c054b544df6ceeb9e612d39af819f4aae, I added a hack to `ConstProp` that skips evaluating ZSTs to avoid that regression. This commit changes `SimplifyLocals` so that it doesn't consider writes of const values to a local to be a use of that local. In doing so, `SimplifyLocals` is able to remove otherwise unused locals left behind by other optimization passes (`ConstProp` in particular). 2019-10-17 18:46:51 +08:00			`let _fn = std::ptr::drop_in_place::<[String]> as unsafe fn(_);`
Add test for slice drop shims 2019-03-31 01:18:54 +08:00			`}`