summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2018-09-30 18:31:03 +0000
committerMartin Storsjo <martin@martin.st>2018-09-30 18:31:03 +0000
commit0f8f0d6d1df8d17765ea5b34b117d85142b2bf24 (patch)
tree4cd6ca2f37ef0e8c11f73439dc771650e886cddc /lldb/packages/Python/lldbsuite/test/python_api/thread
parentb1108399bd66ba9703f6bc671764a6f168f1138b (diff)
downloadbcm5719-llvm-0f8f0d6d1df8d17765ea5b34b117d85142b2bf24.tar.gz
bcm5719-llvm-0f8f0d6d1df8d17765ea5b34b117d85142b2bf24.zip
[COFF] In MinGW mode, ignore relocations against a discarded section
When GCC produces a jump table as part of a comdat function, the jump table itself is produced as plain non-comdat rdata section. When linked with ld.bfd, all of those rdata sections are kept, with relocations unchanged in the sections that refer to discarded comdat sections. This has been observed with at least GCC 5.x and 7.x. Differential Revision: https://reviews.llvm.org/D52600 llvm-svn: 343422
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud