char16_t and char32_t are still mangled as a vendor extension in the 4.4 sources. This is a blocker for 4.4; we need a standard mangling before it is released in order to avoid binary incompatibility with future releases.
The vendor extension mangling was based on the following email as feedback on the original patch: http://gcc.gnu.org/ml/gcc-patches/2008-03/msg01622.html The original suggested mangling was: char16_t -> k char32_t -> q I believe that there was some potential contention on using 'q' due to another proposal requesting that same symbol. Is there any information from the ABI committee on which symbols can be used for the mangling of these two types?
Marked as regression to show up in the important bug list.
Of course involves also libstdc++-v3, its exports.
The trunk now mangles char16_t as Ds and char32_t as Di. Can this be closed?
Yep.