summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStdStringFunction.py
diff options
context:
space:
mode:
authorRafael Espindola <rafael.espindola@gmail.com>2016-05-16 21:14:24 +0000
committerRafael Espindola <rafael.espindola@gmail.com>2016-05-16 21:14:24 +0000
commite64619ce6e9a67354668790e842d9313e3ac6e74 (patch)
tree5c9d3dbfd5a7aac81b553919df823caa0340f243 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStdStringFunction.py
parent01704bb1dbc3febdd7eb09ed0cd8f3ee65be5e98 (diff)
downloadbcm5719-llvm-e64619ce6e9a67354668790e842d9313e3ac6e74.tar.gz
bcm5719-llvm-e64619ce6e9a67354668790e842d9313e3ac6e74.zip
Fail early on unknown appending linkage variables.
In practice only a few well known appending linkage variables work. Currently if codegen sees an unknown appending linkage variable it will just print it as a regular global. That is wrong as the symbol in the produced object file has different semantics as the one provided by the appending linkage. This just errors early instead of producing a broken .o. llvm-svn: 269706
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStdStringFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud