[cfe-commits] [Windows] Properly mangle templates

[John McCall]

On May 24, 2012, at 1:22 PM, João Matos wrote:
> By the way, Timur, how are you testing the symbol mangling?
> 
> I did not find an easy to dump the mangling from cl.exe compiled
> object files. I tried DUMPBIN.exe, but it outputs a lot of unrelated
> stuff, I tried different parameters but did not find much a clean way
> to do it.
> 
> I'm thinking of a way to make a simple test tool so I can more easily
> mangle a lot of declarations and test them automatically, to ensure
> Clang is doing the right thing. This is important to me, since for my
> needs, Clang must match Microsoft compiler's name exactly. Any
> thoughts on a simple way to do this? It could even be used to generate
> Clang test cases.
> 
> Also I noticed it outputs the mangled name with a "\1" marker as the
> first character. I suggest we don't do that in the mangler, since it's
> a specific thing for LLVM. That can be done by the code generator
> instead of the mangler, just makes it cleaner for those who need to
> get the mangled name. If it's okay to change, I'll send a patch for
> it.

Clients need some way of knowing that the symbol does not undergo
C symbol munging.  Yes, we could pass that back as a separate flag,
but is that actually better than recognizing \1?

John.