This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Detect libunwind features allowing LLVMs libunwind to be used #3045
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benpye
force-pushed
the
allow-llvm-unwind
branch
from
0530b38 to
c068030
Compare
|
@janvorli PTLA |
|
LGTM, thank you for doing this! |
jkotas
added a commit
that referenced
this pull request
Feb 5, 2016
Detect libunwind features allowing LLVMs libunwind to be used
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
This allows for LLVMs libunwind to be used. This detects the available libunwind libraries and if the remote unwind and context pointer features are implemented, mostly by adding configure checks to toggle the current OS X workarounds. See issue #872 for some of the motivation behind this, it may also help for #2910.