[LLVMdev] Naming of types by DragonEgg vs. LLVM-GCC
anton at korobeynikov.info
Thu Apr 28 03:58:29 PDT 2011
> With the LLVM-GCC version I could easily get type for "struct.Vector<String>". With the
> DragonEgg version I would need another mapping from that name to "2". The same problem
> can be seen with the "struct.ARPResponder::Entry" becoming just "struct.Entry".
This is pretty much expected.
> Is there a way to make DragonEgg name the types the same way LLVM-GCC does, preserving
> C++ naming a bit more?
The naming of types is arbitrary, you should not rely on them at all.
Use debug information if you really want to know the name of
underlying type, etc.
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
More information about the llvm-dev