mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-24 11:42:57 +01:00
37ae5d8646
llvm-undname used to put '\x' in front of every pair of nibbles, but u"\xD7\xFF" produces a string with 6 bytes: \xD7 \0 \xFF \0 (and \0\0). Correct for a single character (plus terminating \0) is u\xD7FF instead. Now, wchar_t, char16_t, and char32_t strings roundtrip from source to clang-cl (and cl.exe) and then llvm-undname. (...at least as long as it's not a string like L"\xD7FF" L"foo" which gets demangled as L"\xD7FFfoo", where the compiler then considers the "f" as part of the hex escape. That seems ok.) Also add a comment saying that the "almost-valid" char32_t string I added in my last commit is actually produced by compilers. llvm-svn: 358857 |
||
---|---|---|
.. | ||
invalid-manglings.test | ||
ms-arg-qualifiers.test | ||
ms-back-references.test | ||
ms-basic.test | ||
ms-conversion-operators.test | ||
ms-cxx11.test | ||
ms-cxx14.test | ||
ms-cxx17-noexcept.test | ||
ms-mangle.test | ||
ms-md5.test | ||
ms-nested-scopes.test | ||
ms-operators.test | ||
ms-return-qualifiers.test | ||
ms-string-literals.test | ||
ms-template-callback.test | ||
ms-templates-memptrs-2.test | ||
ms-templates-memptrs.test | ||
ms-templates.test | ||
ms-thunks.test | ||
ms-windows.test |