summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/section
diff options
context:
space:
mode:
authorJosh Kunz <jkz@google.com>2019-11-15 17:53:55 -0800
committerJosh Kunz <jkz@google.com>2019-11-22 15:33:13 -0800
commit6551ac7489fe070a2edcfac88f68c93321cba9a9 (patch)
tree76a766ed219d6fc623bc6515e782a4f17ba8cf55 /lldb/packages/Python/lldbsuite/test/python_api/section
parent1668685118cd509d85e5242fa5742bccb3a4aba7 (diff)
downloadbcm5719-llvm-6551ac7489fe070a2edcfac88f68c93321cba9a9.tar.gz
bcm5719-llvm-6551ac7489fe070a2edcfac88f68c93321cba9a9.zip
[Driver] Make -static-libgcc imply static libunwind
In the GNU toolchain, `-static-libgcc` implies that the unwindlib will be linked statically. However, when `--unwindlib=libunwind`, this flag is ignored, and a bare `-lunwind` is added to the linker args. Unfortunately, this means that if both `libunwind.so`, and `libunwind.a` are present in the library path, `libunwind.so` will be chosen in all cases where `-static` is not set. This change makes `-static-libgcc` affect the `-l` flag produced by `--unwindlib=libunwind`. After this patch, providing `-static-libgcc --unwindlib=libunwind` will cause the driver to explicitly emit `-l:libunwind.a` to statically link libunwind. For all other cases it will emit `-l:libunwind.so` matching current behavior with a more explicit link line. https://reviews.llvm.org/D70416
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/section')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud