Comment 42 for bug 1488254

Revision history for this message
In , Lighttpd-2 (lighttpd-2) wrote :

(In reply to comment #39)
> (In reply to comment #38)
> > The new ABI requires the full gcc abi-tag support to be compatible with
> > gcc. If you compile everything with clang and disable dual ABI support
> > you can get away with less, but what is the point? Just use the clang
> > libc++ instead, which requires no changes.
>
> [...]
>
> We need libc++ to work on the supported architectures with and without GNU
> libraries. Getting rid of the GNU counterparts is out of the question for
> any practical purpose.

So you're saying there is a use case to compile everything with clang and libstdc++? If that is actually something you need, and you don't need to be compatible to any name mangling, you just need the part of the patch in D12834 accepting abi tags and you should be fine (no dual ABI support ofc); no modifications to the name mangling (lib/AST/ItaniumMangle.cpp) are necessary for that.