Nico Weber 37ae5d8646 llvm-undname: Fix hex escapes in wchar_t, char16_t, char32_t strings ... 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		2019-04-21 17:19:27 +00:00
..
CMakeLists.txt	Move demangling function from llvm-objdump to Demangle library	2019-01-17 15:18:44 +00:00
Demangle.cpp	Add missing include (cstdlib) to Demangle.h	2019-01-22 19:18:18 +00:00
ItaniumDemangle.cpp	Update more file headers across all of the LLVM projects in the monorepo	2019-01-19 10:56:40 +00:00
LLVMBuild.txt	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00
MicrosoftDemangle.cpp	llvm-undname: Fix hex escapes in wchar_t, char16_t, char32_t strings	2019-04-21 17:19:27 +00:00
MicrosoftDemangleNodes.cpp	Update more file headers across all of the LLVM projects in the monorepo	2019-01-19 10:56:40 +00:00