summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/expr-in-syscall/main.cpp
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2018-03-14 20:17:16 +0000
committerMartin Storsjo <martin@martin.st>2018-03-14 20:17:16 +0000
commit5351891b553e6bb6bd0cb1e8c2c99128c75cc76e (patch)
treeb0d96389c5ba2b57c3bde3cbbf5e0cc36f9a2f85 /lldb/packages/Python/lldbsuite/test/expression_command/expr-in-syscall/main.cpp
parent36f678b48a3055434ce771bd9e2f9c93fe93ad38 (diff)
downloadbcm5719-llvm-5351891b553e6bb6bd0cb1e8c2c99128c75cc76e.tar.gz
bcm5719-llvm-5351891b553e6bb6bd0cb1e8c2c99128c75cc76e.zip
[COFF] Add support for the GNU ld flag --kill-at
GNU ld has got a number of different flags for adjusting how to behave around stdcall functions. The --kill-at flag strips the trailing sdcall suffix from exported functions (which otherwise is included by default in MinGW setups). This also strips it from the corresponding import library though. That makes it hard to link to such an import library from code that calls the functions - but this matches what GNU ld does with this flag. Therefore, this flag is probably not sensibly used together with import libraries, but probably mostly when creating some sort of plugin, or if creating the import library separately with dlltool. Differential Revision: https://reviews.llvm.org/D44292 llvm-svn: 327561
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/expr-in-syscall/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud