[LLVMdev] C++ demangling in LLVM

Jean-Daniel Dupas devlists at shadowlab.org
Thu Jul 5 00:05:08 PDT 2012


Isn't __cxa_demangle already available to all libc++/libstdc++ client ? Linking on one if this library should be enough to get it.

Le 5 juil. 2012 à 08:34, Chandler Carruth a écrit :

> 
> On Wed, Jul 4, 2012 at 11:18 PM, Alexey Samsonov <samsonov at google.com> wrote:
> 
> On Thu, Jul 5, 2012 at 9:08 AM, Chandler Carruth <chandlerc at google.com> wrote:
> In the same way that the core LLVM libraries have support routines for DWARF, I think that both mangling and demangling should be provided as well. I suspect that the 'Support' library is the best we have, although eventually we need to split this library up a bit. That's not really your problem though.
> 
> The bigger problem is that we don't have any good way of sharing code between runtime libraries (such as libcxxabi, sanitizer runtimes, etc) and LLVM.
> 
> Yes, surely I want this to happen and would be happy to help if you (or someone else) give some advice or guidance.
> 
> Did you see my proposal to llvmdev some time ago about how to do this? If you have thoughts about that, we should move the discussion to that thread.
>  
> 
> 
> One somewhat interesting question, would the APIs exposed by libcxxabi be sufficient for the sanitizer runtimes?
> 
> How can we use libcxxabi anyway? I mean, is it shipped with compiler so that we can make Clang driver tell to link user program with
> libcxxabi in the same way we tell it to link with sanitizer runtimes if flags -fwhatever-sanitizer is present?
> 
> Essentially, it could be. It's more complicated than just that though, so I was just curious if it would work.
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

-- Jean-Daniel




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120705/e6480d26/attachment.html>


More information about the llvm-dev mailing list