diff options
| author | Teresa Johnson <tejohnson@google.com> | 2016-07-13 16:35:56 +0000 |
|---|---|---|
| committer | Teresa Johnson <tejohnson@google.com> | 2016-07-13 16:35:56 +0000 |
| commit | b907d06151623e17bd7755de4d6f52290e14de09 (patch) | |
| tree | 104bfb92cfff22feade2366356ea85ec6af7a13c /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py | |
| parent | 610a2f65253526b866c230132cde8595a7303376 (diff) | |
| download | bcm5719-llvm-b907d06151623e17bd7755de4d6f52290e14de09.tar.gz bcm5719-llvm-b907d06151623e17bd7755de4d6f52290e14de09.zip | |
[ThinLTO/gold] Enable symbol resolution in distributed backend case
While testing a follow-on change to enable index-based symbol resolution
and internalization in the distributed backends, I realized that a test
case change I made in r275247 was only required because we were not
analyzing symbols in the claimed files in thinlto-index-only mode.
In the fixed test case there should be no internalization because we are
linking in -shared mode, so f() is in fact exported, which is detected
properly when we analyze symbols in thinlto-index-only mode. Note that
this is not (yet) a correctness issue (because we are not yet performing
the index-based linkage optimizations in the distributed backends -
that's coming in a follow-on patch).
llvm-svn: 275277
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
