summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2018-08-17 16:14:05 +0000
committerZachary Turner <zturner@google.com>2018-08-17 16:14:05 +0000
commit3461bfaa9cc7766330b3539b02b65c0ebf85755a (patch)
tree4086459b2390dc97498e8708a3ad7efb46c98579 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
parente02ee4f013632aac34e1fb84d868984a91773e2a (diff)
downloadbcm5719-llvm-3461bfaa9cc7766330b3539b02b65c0ebf85755a.tar.gz
bcm5719-llvm-3461bfaa9cc7766330b3539b02b65c0ebf85755a.zip
[MS Demangler] Rework the way operators are demangled.
Previously, some of the code for actually parsing mangled operator names was more like formatting code in nature, and was interspersed with the demangling code which builds the AST. This means that by the time we got to the printing code, we had lost all information about what type of operator we had, and all we were left with was a string that we just had to print. However, not all operators are actually even operators. it's basically just a catch-all mangling for "special names", and for some of the other types it helps to know when we're actually doing the printing what it is. This patch changes the way things work by introducing an OperatorInfo structure and corresponding enumeration. When we demangle we store the enumeration value and demangled components separately. This gives more flexibility during printing. In doing so, some demanglings of special names which we didn't previously support come out of this for free, so we now demangle those. A few are more complex and are better left for a followup patch though. An exhaustive test of every possible operator code is included, with the ones that don't yet work commented out. llvm-svn: 340046
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud