summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorPuyan Lotfi <puyan@puyan.org>2019-11-19 03:07:47 -0500
committerPuyan Lotfi <puyan@puyan.org>2019-11-19 17:47:38 -0500
commitea8e02822341e2421b94167d828d3f224e767424 (patch)
tree95fb3032bd212034ddea71e6e64f6a3386e3fd49 /lldb/packages/Python/lldbsuite/test
parent70c68a6b0e515967dba5b30f6a60e220a8cd8d2c (diff)
downloadbcm5719-llvm-ea8e02822341e2421b94167d828d3f224e767424.tar.gz
bcm5719-llvm-ea8e02822341e2421b94167d828d3f224e767424.zip
[clang][IFS] Driver Pipeline: generate stubs after standard pipeline (2)
Second Landing Attempt: 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. Differential Revision: https://reviews.llvm.org/D70274
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud