2024-02-22 12:10:29 +00:00
|
|
|
//@ compile-flags: -C no-prepopulate-passes -Zmir-opt-level=0 -Copt-level=0
|
2015-10-01 09:55:52 +00:00
|
|
|
|
|
|
|
|
#![crate_type = "lib"]
|
|
|
|
|
|
|
|
|
|
// Hack to get the correct size for the length part in slices
|
2022-12-30 20:11:30 +00:00
|
|
|
// CHECK: @helper([[USIZE:i[0-9]+]] %_1)
|
2015-10-01 09:55:52 +00:00
|
|
|
#[no_mangle]
|
2017-10-30 17:18:00 +00:00
|
|
|
pub fn helper(_: usize) {
|
2015-10-01 09:55:52 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// CHECK-LABEL: @ref_dst
|
|
|
|
|
#[no_mangle]
|
|
|
|
|
pub fn ref_dst(s: &[u8]) {
|
|
|
|
|
// We used to generate an extra alloca and memcpy to ref the dst, so check that we copy
|
|
|
|
|
// directly to the alloca for "x"
|
Separate immediate and in-memory ScalarPair representation
Currently, we assume that ScalarPair is always represented using
a two-element struct, both as an immediate value and when stored
in memory.
This currently works fairly well, but runs into problems with
https://github.com/rust-lang/rust/pull/116672, where a ScalarPair
involving an i128 type can no longer be represented as a two-element
struct in memory. For example, the tuple `(i32, i128)` needs to be
represented in-memory as `{ i32, [3 x i32], i128 }` to satisfy
alignment requirement. Using `{ i32, i128 }` instead will result in
the second element being stored at the wrong offset (prior to
LLVM 18).
Resolve this issue by no longer requiring that the immediate and
in-memory type for ScalarPair are the same. The in-memory type
will now look the same as for normal struct types (and will include
padding filler and similar), while the immediate type stays a
simple two-element struct type. This also means that booleans in
immediate ScalarPair are now represented as i1 rather than i8,
just like we do everywhere else.
The core change here is to llvm_type (which now treats ScalarPair
as a normal struct) and immediate_llvm_type (which returns the
two-element struct that llvm_type used to produce). The rest is
fixing things up to no longer assume these are the same. In
particular, this switches places that try to get pointers to the
ScalarPair elements to use byte-geps instead of struct-geps.
2023-12-15 11:14:39 +00:00
|
|
|
// CHECK: store ptr %s.0, {{.*}} %x
|
|
|
|
|
// CHECK: [[X1:%[0-9]+]] = getelementptr inbounds i8, {{.*}} %x, {{i32 4|i64 8}}
|
2022-02-21 10:21:23 +00:00
|
|
|
// CHECK: store [[USIZE]] %s.1, {{.*}} [[X1]]
|
2016-08-24 03:36:37 +00:00
|
|
|
|
2015-10-01 09:55:52 +00:00
|
|
|
let x = &*s;
|
2016-08-24 03:36:37 +00:00
|
|
|
&x; // keep variable in an alloca
|
2015-10-01 09:55:52 +00:00
|
|
|
}
|