search for: _ztsfie

...and we don’t want to copy the actual function bodies to the merged module. Indirect call targets can be represented in the following way using named metadata: void foo() {} int bar() { return 0; } # Merged module !cfi.functions = !{!1, !3} !1 = !{!"bar", i8 0, !2} !2 = !{i64 0, !"_ZTSFiE"} !3 = !{!"foo", i8 0, !4} !4 = !{i64 0, !"_ZTSFvE"} Each function is described by a tuple of * Promoted name as a string * Linkage (see below) * Type(s) A function can have multiple types. In the Cross-DSO mode each function has a second “external” numeric type, and we...

...direct call targets can be represented in the following way using >> named metadata: >> >> void foo() {} >> int bar() { return 0; } >> >> # Merged module >> !cfi.functions = !{!1, !3} >> !1 = !{!"bar", i8 0, !2} >> !2 = !{i64 0, !"_ZTSFiE"} >> !3 = !{!"foo", i8 0, !4} >> !4 = !{i64 0, !"_ZTSFvE"} > > > Presumably there would be no entries in !cfi.functions for functions defined > in the merged module, as the type metadata would come from the module > itself. Right. The same as wit...

...t; named metadata: > >>> > >>> void foo() {} > >>> int bar() { return 0; } > >>> > >>> # Merged module > >>> !cfi.functions = !{!1, !3} > >>> !1 = !{!"bar", i8 0, !2} > >>> !2 = !{i64 0, !"_ZTSFiE"} > >>> !3 = !{!"foo", i8 0, !4} > >>> !4 = !{i64 0, !"_ZTSFvE"} > >> > >> > >> Presumably there would be no entries in !cfi.functions for functions > defined > >> in the merged module, as the type metadata woul...