mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d06ca0ffaf
rust/tests/codegen/loads.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

153 lines
4.2 KiB
Rust
Raw Normal View History

simplify-locals: Remove unused assignments regardless of rvalue kind
2020-10-16 19:00:00 -05:00
// compile-flags: -C no-prepopulate-passes -Zmir-opt-level=0
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
Avoid loading the whole gdb debug scripts section. This is so LLVM isn't forced to load every byte of it. Also sets the alignment of the load. Adds a test for the debug script section.
2015-09-15 16:22:16 -05:00
#![crate_type = "lib"]
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
use std::mem::MaybeUninit;
use std::num::NonZeroU16;
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
pub struct Bytes {
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
a: u8,
b: u8,
c: u8,
d: u8,
}
#[derive(Copy, Clone)]
pub enum MyBool {
True,
False,
}
Add !align metadata on loads of &/&mut/Box Note that this refers to the alignment of what the loaded value points to, _not_ the alignment of the loaded value itself.
2022-02-15 22:45:09 -06:00
#[repr(align(16))]
pub struct Align16(u128);
Update some codegen tests for opaque pointers
2022-02-21 04:21:23 -06:00
// CHECK: @ptr_alignment_helper({{.*}}align [[PTR_ALIGNMENT:[0-9]+]]
Add !align metadata on loads of &/&mut/Box Note that this refers to the alignment of what the loaded value points to, _not_ the alignment of the loaded value itself.
2022-02-15 22:45:09 -06:00
#[no_mangle]
pub fn ptr_alignment_helper(x: &&()) {}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
// CHECK-LABEL: @load_ref
#[no_mangle]
pub fn load_ref<'a>(x: &&'a i32) -> &'a i32 {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %x, align [[PTR_ALIGNMENT]], !nonnull !{{[0-9]+}}, !align ![[ALIGN_4_META:[0-9]+]], !noundef !{{[0-9]+}}
Add !align metadata on loads of &/&mut/Box Note that this refers to the alignment of what the loaded value points to, _not_ the alignment of the loaded value itself.
2022-02-15 22:45:09 -06:00
*x
}
// CHECK-LABEL: @load_ref_higher_alignment
#[no_mangle]
pub fn load_ref_higher_alignment<'a>(x: &&'a Align16) -> &'a Align16 {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %x, align [[PTR_ALIGNMENT]], !nonnull !{{[0-9]+}}, !align ![[ALIGN_16_META:[0-9]+]], !noundef !{{[0-9]+}}
Add !align metadata on loads of &/&mut/Box Note that this refers to the alignment of what the loaded value points to, _not_ the alignment of the loaded value itself.
2022-02-15 22:45:09 -06:00
*x
}
// CHECK-LABEL: @load_scalar_pair
#[no_mangle]
pub fn load_scalar_pair<'a>(x: &(&'a i32, &'a Align16)) -> (&'a i32, &'a Align16) {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %{{.+}}, align [[PTR_ALIGNMENT]], !nonnull !{{[0-9]+}}, !align ![[ALIGN_4_META]], !noundef !{{[0-9]+}}
// CHECK: load ptr, ptr %{{.+}}, align [[PTR_ALIGNMENT]], !nonnull !{{[0-9]+}}, !align ![[ALIGN_16_META]], !noundef !{{[0-9]+}}
Add !align metadata on loads of &/&mut/Box Note that this refers to the alignment of what the loaded value points to, _not_ the alignment of the loaded value itself.
2022-02-15 22:45:09 -06:00
*x
}
// CHECK-LABEL: @load_raw_pointer
#[no_mangle]
pub fn load_raw_pointer<'a>(x: &*const i32) -> *const i32 {
Improve comments
2022-12-30 14:11:17 -06:00
// loaded raw pointer should not have !nonnull or !align metadata
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %x, align [[PTR_ALIGNMENT]], !noundef ![[NOUNDEF:[0-9]+]]{{$}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_box
#[no_mangle]
pub fn load_box<'a>(x: Box<Box<i32>>) -> Box<i32> {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %{{.*}}, align [[PTR_ALIGNMENT]], !nonnull !{{[0-9]+}}, !align ![[ALIGN_4_META]], !noundef !{{[0-9]+}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_bool
#[no_mangle]
pub fn load_bool(x: &bool) -> bool {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i8, ptr %x, align 1, !range ![[BOOL_RANGE:[0-9]+]], !noundef !{{[0-9]+}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_maybeuninit_bool
#[no_mangle]
pub fn load_maybeuninit_bool(x: &MaybeUninit<bool>) -> MaybeUninit<bool> {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i8, ptr %x, align 1{{$}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_enum_bool
#[no_mangle]
pub fn load_enum_bool(x: &MyBool) -> MyBool {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i8, ptr %x, align 1, !range ![[BOOL_RANGE]], !noundef !{{[0-9]+}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_maybeuninit_enum_bool
#[no_mangle]
pub fn load_maybeuninit_enum_bool(x: &MaybeUninit<MyBool>) -> MaybeUninit<MyBool> {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i8, ptr %x, align 1{{$}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_int
#[no_mangle]
pub fn load_int(x: &u16) -> u16 {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i16, ptr %x, align 2, !noundef ![[NOUNDEF]]{{$}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_nonzero_int
#[no_mangle]
pub fn load_nonzero_int(x: &NonZeroU16) -> NonZeroU16 {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i16, ptr %x, align 2, !range ![[NONZEROU16_RANGE:[0-9]+]], !noundef !{{[0-9]+}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
}
// CHECK-LABEL: @load_option_nonzero_int
#[no_mangle]
pub fn load_option_nonzero_int(x: &Option<NonZeroU16>) -> Option<NonZeroU16> {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load i16, ptr %x, align 2, !noundef ![[NOUNDEF]]{{$}}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
*x
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
}
// CHECK-LABEL: @borrow
#[no_mangle]
pub fn borrow(x: &i32) -> &i32 {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %x{{.*}}, !nonnull
Disable old trans access via -Z orbit, #[rustc_no_mir] or --disable-orbit.
2016-08-23 22:36:37 -05:00
&x; // keep variable in an alloca
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
x
}
// CHECK-LABEL: @_box
#[no_mangle]
pub fn _box(x: Box<i32>) -> i32 {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: load ptr, ptr %x{{.*}}, align [[PTR_ALIGNMENT]]
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
*x
}
// CHECK-LABEL: small_array_alignment
// The array is loaded as i32, but its alignment is lower, go with 1 byte to avoid target
// dependent alignment
#[no_mangle]
pub fn small_array_alignment(x: [i8; 4]) -> [i8; 4] {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: [[VAR:%[0-9]+]] = load i32, ptr %{{.*}}, align 1
remove box derefs from codgen
2022-05-13 23:53:03 -05:00
// CHECK: ret i32 [[VAR]]
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
x
}
// CHECK-LABEL: small_struct_alignment
// The struct is loaded as i32, but its alignment is lower, go with 1 byte to avoid target
// dependent alignment
#[no_mangle]
pub fn small_struct_alignment(x: Bytes) -> Bytes {
CHECK only for opaque ptr
2023-07-27 16:44:13 -05:00
// CHECK: [[VAR:%[0-9]+]] = load i32, ptr %{{.*}}, align 1
remove box derefs from codgen
2022-05-13 23:53:03 -05:00
// CHECK: ret i32 [[VAR]]
Revamp codegen tests to check IR quality instead of quantity The current codegen tests only compare IR line counts between similar rust and C programs, the latter getting compiled with clang. That looked like a good idea back then, but actually things like lifetime intrinsics mean that less IR isn't always better, so the metric isn't really helpful. Instead, we can start doing tests that check specific aspects of the generated IR, like attributes or metadata. To do that, we can use LLVM's FileCheck tool which has a number of useful features for such tests. To start off, I created some tests for a few things that were recently added and/or broken.
2015-05-24 11:07:52 -05:00
x
}
Apply noundef metadata to loads of types that do not permit raw init This matches the noundef attributes we apply on arguments/return types.
2022-02-12 13:01:33 -06:00
Add !align metadata on loads of &/&mut/Box Note that this refers to the alignment of what the loaded value points to, _not_ the alignment of the loaded value itself.
2022-02-15 22:45:09 -06:00
// CHECK-DAG: ![[BOOL_RANGE]] = !{i8 0, i8 2}
// CHECK-DAG: ![[NONZEROU16_RANGE]] = !{i16 1, i16 0}
// CHECK-DAG: ![[ALIGN_4_META]] = !{i64 4}
// CHECK-DAG: ![[ALIGN_16_META]] = !{i64 16}
Reference in New Issue Copy Permalink