Apart from the convenience, is there any benefit of using stack_load
and stack_store
as opposed to stack_addr
and then load
and store
? In other words, if I have a type that can be either on the stack or a pointer to somewhere else, is it worth the inconvenience to track whether it's on the stack so that stack_load
and stack_store
can be used?
Not really right now. stack_load/stack_store is lowered to stack_addr+load/store with memflags of notrap and aligned in the backend.
Veverak has marked this topic as resolved.
Last updated: Dec 23 2024 at 12:05 UTC