summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorPuyan Lotfi <puyan@puyan.org>2019-11-20 14:41:11 -0500
committerPuyan Lotfi <puyan@puyan.org>2019-11-20 16:22:50 -0500
commit73429126c91c2065c6f6ef29b3eec1b7798502bb (patch)
tree133939f108fafa9e3f024ab46239f7e1629889bf /lldb/packages/Python/lldbsuite/test/python_api
parentc8dfe907299e16aeb17175cb0896c17043fc7c81 (diff)
downloadbcm5719-llvm-73429126c91c2065c6f6ef29b3eec1b7798502bb.tar.gz
bcm5719-llvm-73429126c91c2065c6f6ef29b3eec1b7798502bb.zip
[clang][IFS] Driver Pipeline: generate stubs after standard pipeline (3)
Third Landing Attempt (dropping any linker invocation from clang driver): Up until now, clang interface stubs has replaced the standard PP -> C -> BE -> ASM -> LNK pipeline. With this change, it will happen in conjunction with it. So what when you build your code you will get an a.out or lib.so as well as an interface stub file. Example: clang -shared -o libfoo.so -emit-interface-stubs ... will generate both a libfoo.so and a libfoo.ifso. The .so file will contain the code from the standard compilation pipeline and the .ifso file will contain the ELF stub library. Note: For driver-test.c I've added -S in order to prevent any bot failures on bots that don't have the proper linker for their native triple. You could always specify a triple like x86_64-unknown-linux-gnu and on bots like x86_64-scei-ps4 the clang driver would invoke regular ld instead of getting the error 'Executable "orbis-ld" doesn't exist!' but on bots like ppc64be and s390x you'd get an error "/usr/bin/ld: unrecognised emulation mode: elf_x86_64" Differential Revision: https://reviews.llvm.org/D70274
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud