Skip to content

Conversation

@aschwaighofer
Copy link

When references to the symbol swift_async_extendedFramePointerFlags
are emitted they have to be weak.

References to the symbol swift_async_extendedFramePointerFlags get
emitted only by frame lowering code. Therefore, the backend needs to track
references to the symbol and mark them weak.

Differential Revision: https://reviews.llvm.org/D115672

rdar://86432570

@aschwaighofer
Copy link
Author

@swift-ci test

…terFlags weak if it emits it

When references to the symbol `swift_async_extendedFramePointerFlags`
are emitted they have to be weak.

References to the symbol `swift_async_extendedFramePointerFlags` get
emitted only by frame lowering code. Therefore, the backend needs to track
references to the symbol and mark them weak.

Differential Revision: https://reviews.llvm.org/D115672

rdar://86432570
@aschwaighofer aschwaighofer force-pushed the weak_swift_async_extendedFramePointerFlags_rdar_86432570_20210726 branch from a4929ac to b1368f1 Compare December 15, 2021 16:20
@aschwaighofer
Copy link
Author

@swift-ci test

@aschwaighofer aschwaighofer merged commit e7c56da into swiftlang:stable/20210726 Dec 15, 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