[Lldb-commits] [PATCH] Patch for LLDB demangler for demangling upon actual language
engineer.developer at gmail.com
Wed Feb 4 07:37:19 PST 2015
In http://reviews.llvm.org/D7302#116129, @clayborg wrote:
> To make my comments clearer:
> 1 - Can't we tell the language by looking at the Mangled prefix? "_Z" = C++, "$" = C++?
> 2 - Where do we need to know the language? I the JIT? If so we might need a new MangledWithLanguage class and use it only where we need it so it doesn't make lldb_private::Symbol and lldb_private::Function and lldb_private::Block's inlined info take up more space. We spent a lot of time doing memory analysis on LLDB and lldb_private::Symbol objects were consistently at the top of the heap.
1 - No - because, for example, Delphi use same mangling, but has thin differences in types name demangling and namespace separator (same with Java).
2 - We need to know exact language for given function or method name demangling with its parameters types on full header.
More information about the lldb-commits