summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/SelectionDAG/LegalizeVectorOps.cpp
diff options
context:
space:
mode:
authorEd Schouten <ed@nuxi.nl>2017-02-15 21:51:25 +0000
committerEd Schouten <ed@nuxi.nl>2017-02-15 21:51:25 +0000
commit3bf713043aab3b5acd848c9dbc8c311002bde36d (patch)
tree76196a86fe307905cb7b7f53c4bec385d37dd183 /llvm/lib/CodeGen/SelectionDAG/LegalizeVectorOps.cpp
parentd122abead411bd4bb8b81311287e94f31cd8408b (diff)
downloadbcm5719-llvm-3bf713043aab3b5acd848c9dbc8c311002bde36d.tar.gz
bcm5719-llvm-3bf713043aab3b5acd848c9dbc8c311002bde36d.zip
Make --export-dynamic work on non-PIC/PIE targets.
For CloudABI I'm only interested in generating non-PIC/PIE executables on armv6 and i686, as PIE introduces larger overhead than on aarch64 and x86_64. Still, I want to be able to instruct the linker to generate a dynamic symbol table if requested. One example use for this is that dynamic symbol tables can be used by programs to print nicely formatted stacktraces, including symbol names. Right now there seems to be some logic in LLD that it only wants to emit dynamic symbol tables when either linking against libraries or when building PIC. Let's extend this to also take --export-dynamic into account. Reviewed by: ruiu Differential Revision: https://reviews.llvm.org/D29982 llvm-svn: 295240
Diffstat (limited to 'llvm/lib/CodeGen/SelectionDAG/LegalizeVectorOps.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud