-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Add flag -swift-async-framepointer=auto,never,always to control swift extended frame information emission #39245
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
Add flag -swift-async-framepointer=auto,never,always to control swift extended frame information emission #39245
Conversation
test with swiftlang/llvm-project#3245 @swift-ci test |
Build failed |
test with swiftlang/llvm-project#3245 @swift-ci test |
Build failed |
592704e
to
fad16c8
Compare
test with swiftlang/llvm-project#3245 @swift-ci test |
Build failed |
test with swiftlang/llvm-project#3255 @swift-ci test |
control swift extended frame information emission On linux we default to disable the extended frame info (since the system libraries don't support it). On darwin the default is to automatically choose based on the deployment target. The Concurrency library explicitly forces extended frame information and the back deployment library explicitly disables it.
fad16c8
to
a93f777
Compare
@swift-ci test |
This pull breaks building the stdlib with a regular clang, ie not the Swift-forked one, on my Android CI. Since that compatibility has been maintained so far, maybe a new CMake flag can be added to only add flags like this for the Swift-forked clang? |
On linux we default to disable the extended frame info (since the system
libraries don't support it).
On darwin the default is to automatically choose based on the deployment target.
The Concurrency library explicitly forces extended frame information and the
back deployment library explicitly disables it.