[AddressLowering] Omit dealloc_stack in dead ends. #62453
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is valid for owned values not to be destroyed on paths terminating in
unreachable
. Similarly, it is valid for storage not to be deallocated on paths terminating inunreachable
. However, it is not valid for storage to be deallocated before being deinitialized, even in paths terminating inunreachable
. Consequently, when AddressLowering,dealloc_stack
s must not be created in dead-end blocks: because the input OSSA may not destroy an owned value, the output may not deinitialize owned storage; so adealloc_stack
in anunreachable
block could dealloc storage which was not deinitialized.