summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/dynamic-value-same-basename
diff options
context:
space:
mode:
authorReid Kleckner <rnk@google.com>2018-03-16 20:13:32 +0000
committerReid Kleckner <rnk@google.com>2018-03-16 20:13:32 +0000
commitf8b51c5f90c60aceedef9ed185eeac58f501075a (patch)
treed08c0ba7c58042894bbc7c617da3456e555034cd /lldb/packages/Python/lldbsuite/test/lang/cpp/dynamic-value-same-basename
parent2aeb930a9f5761e39fb321ad61710683fb49009d (diff)
downloadbcm5719-llvm-f8b51c5f90c60aceedef9ed185eeac58f501075a.tar.gz
bcm5719-llvm-f8b51c5f90c60aceedef9ed185eeac58f501075a.zip
[IR] Avoid the need to prefix MS C++ symbols with '\01'
Now the Windows mangling modes ('w' and 'x') do not do any mangling for symbols starting with '?'. This means that clang can stop adding the hideous '\01' leading escape. This means LLVM debug logs are less likely to contain ASCII escape characters and it will be easier to copy and paste MS symbol names from IR. Finally. For non-Windows platforms, names starting with '?' still get IR mangling, so once clang stops escaping MS C++ names, we will get extra '_' prefixing on MachO. That's fine, since it is currently impossible to construct a triple that uses the MS C++ ABI in clang and emits macho object files. Differential Revision: https://reviews.llvm.org/D7775 llvm-svn: 327734
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/dynamic-value-same-basename')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud