search for: updatetypeidentifiers

...can continue as usual. This requires clang to generate a cross-CU unique identifier for C types (one simple scheme is using a identifier that is unique within the CU and concatenating the CU's file name). And it also requires hashing of C types at DebugInfo IR level. We can add an API such as updateTypeIdentifiers(Module *), linker can call it right before linking in a source module. This is a preliminary design to start discussion. Comments and feedback are welcome. Thanks, Manman -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/...

...> This requires clang to generate a cross-CU unique identifier for C types > (one simple scheme is using a identifier that is unique within the CU and > concatenating the CU's file name). And it also requires hashing of C types > at DebugInfo IR level. We can add an API such as > updateTypeIdentifiers(Module *), linker can call it right before linking in > a source module. > I think the easiest design you'll get for uniquing C types that are named the same thing (i.e. type defined in a .h file) is to use the name of the struct combined with the file (and possibly line/column) as an id...

...to generate a cross-CU unique identifier for C types > > (one simple scheme is using a identifier that is unique within the CU and > > concatenating the CU's file name). And it also requires hashing of C > types > > at DebugInfo IR level. We can add an API such as > > updateTypeIdentifiers(Module *), linker can call it right before linking > in > > a source module. > > > > I think the easiest design you'll get for uniquing C types that are > named the same thing (i.e. type defined in a .h file) is to use the > name of the struct combined with the file (...