search for: typeid_summary_block

...e MDNode by storing a resolution in the combined > summary, and by creating > Assuming I understand this correctly, that means that there would be some kind of type table section in the combined summary index bitcode file, that would look something like the following for the above case: <TYPEID_SUMMARY_BLOCK ...> <TYPE abbrevid=... resolutionid, "typeid3"> </TYPEID_SUMMARY_BLOCK> and included in the on-disk summary as a StringMap, right? > definitions of each of the symbols that shall be required to satisfy the > link time dependencies in the individual ThinLTO mod...

Hi all, As promised, here is a brain dump on how I see CFI for vcalls working under ThinLTO. Most of this has been prototyped, so the design does appear to be sound. For context on how CFI currently works under regular LTO, please read: http://llvm.org/docs/TypeMetadata.html http://clang.llvm.org/docs/ControlFlowIntegrityDesign.html http://clang.llvm.org/docs/LTOVisibility.html ==== Summary