Skip to content

Cap the alignment of spilled values (vs. allocas) at the max frame alignment #3071

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

aschwaighofer
Copy link

Before this patch we would normally use the ABI alignment which can be
to high for the context alginment.

For spilled values we don't need ABI alignment, since the frame entry's
address is not escaped.

rdar://79664965

https://reviews.llvm.org/D105288

@aschwaighofer
Copy link
Author

@swift-ci test

@aschwaighofer aschwaighofer force-pushed the coro_async_alignment_79664965 branch from 52dea54 to 34c2353 Compare July 6, 2021 15:42
@aschwaighofer
Copy link
Author

@swift-ci test

@aschwaighofer aschwaighofer force-pushed the coro_async_alignment_79664965 branch from 34c2353 to 3026438 Compare July 7, 2021 13:45
@aschwaighofer
Copy link
Author

@swift-ci Please test

@aschwaighofer aschwaighofer force-pushed the coro_async_alignment_79664965 branch 2 times, most recently from 7438d49 to 3026438 Compare July 7, 2021 18:16
… max frame alignment

Before this patch we would normally use the ABI alignment which can be
to high for the context alginment.

For spilled values we don't need ABI alignment, since the frame entry's
address is not escaped.

rdar://79664965

Differential Revision: https://reviews.llvm.org/D105288
@aschwaighofer aschwaighofer force-pushed the coro_async_alignment_79664965 branch from 3026438 to c575f28 Compare July 7, 2021 21:49
@aschwaighofer
Copy link
Author

@swift-ci test

@aschwaighofer aschwaighofer merged commit f4d8edd into swiftlang:apple/stable/20210107 Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant