summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2019-07-23 06:38:04 +0000
committerMartin Storsjo <martin@martin.st>2019-07-23 06:38:04 +0000
commit341a68ca2f5b11d83350db22fb4aa1614483c1f3 (patch)
tree667e83774ff4986ebb35fa0bb20386eedcf4e519 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
parenta658cb0b1289ae6137417edda47ab71e525a5a64 (diff)
downloadbcm5719-llvm-341a68ca2f5b11d83350db22fb4aa1614483c1f3.tar.gz
bcm5719-llvm-341a68ca2f5b11d83350db22fb4aa1614483c1f3.zip
[COFF] Unbreak sorting of mingw comdat .tls sections after SVN r363457
Code built for mingw with -fdata-sections will store each TLS variable in a comdat section, named .tls$$<varname>. Normal TLS variables are stored in sections named .tls$ with a trailing dollar, which are sorted after a starter marker (in a later linked object file) in a section named ".tls" (with no dollar suffix), before an ending marker in a section named ".tls$ZZZ". The mingw comdat section suffix stripping introduced in SVN r363457 broke sorting of such tls sections, ending up sorting the stripped .tls$$<varname> sections (stripped to ".tls") before the start marker in the section named ".tls". We could add exceptions to the section name suffix stripping for .tls (and .CRT, where suffixes always should be honored), but the more conservative option is probably the reverse; to only apply the stripping for the normal sections where sorting shouldn't have any effect. Differential Revision: https://reviews.llvm.org/D65018 llvm-svn: 366780
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud