Scott McMurray bf36193ef6 Add a distinct OperandValue::ZeroSized variant for ZSTs ... These tend to have special handling in a bunch of places anyway, so the variant helps remember that. And I think it's easier to grok than non-Scalar Aggregates sometimes being `Immediates` (like I got wrong and caused 109992). As a minor bonus, it means we don't need to generate poison LLVM values for them to pass around in `OperandValue::Immediate`s.		2023-05-31 19:10:28 -07:00
..
const_eval_select.rs	Add more codegen tests	2023-01-17 16:23:22 +01:00
exact_div.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
likely.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
mask.rs	Add more codegen tests	2023-01-17 16:23:22 +01:00
nearby.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
nontemporal.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
offset_from.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
offset.rs	Also use mir::Offset for pointer add	2023-04-27 22:44:42 -07:00
prefetch.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
transmute-niched.rs	assume value ranges in transmute	2023-04-13 00:12:39 -07:00
transmute-x64.rs	Handle not all immediates having abi::Scalars	2023-04-09 11:16:50 -07:00
transmute.rs	Add a distinct OperandValue::ZeroSized variant for ZSTs	2023-05-31 19:10:28 -07:00
unchecked_math.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
volatile_order.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
volatile.rs	Move /src/test to /tests	2023-01-11 09:32:08 +00:00