mirror of
https://github.com/rust-lang/rust.git
synced 2024-12-04 20:54:13 +00:00
c2fd26a115
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. |
||
---|---|---|
.. | ||
compare_bytes.rs | ||
const_eval_select.rs | ||
exact_div.rs | ||
likely.rs | ||
mask.rs | ||
nearby.rs | ||
nontemporal.rs | ||
offset_from.rs | ||
offset.rs | ||
prefetch.rs | ||
transmute-niched.rs | ||
transmute-x64.rs | ||
transmute.rs | ||
unchecked_math.rs | ||
volatile_order.rs | ||
volatile.rs |