search for: baralias

...otTracker, and prefixing them with a special character. Avoiding characters already used in some fashion (i.e. “!” for metadata and “#” for attributes), I initially have chosen “^”. Open to suggestions though.Consider the following example:extern void foo();int X;int bar() { foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int main() { barAlias(); return bar();}The proposed format has one entry per ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = gv: {guid: 1881667236089500162, name: X,...

...special character. Avoiding >> characters already used in some fashion (i.e. “!” for metadata and “#” for >> attributes), I initially have chosen “^”. Open to suggestions >> though.Consider the following example:extern void foo();int X;int bar() { >> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >> main() { barAlias(); return bar();}The proposed format has one entry per >> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >> like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = gv: {guid: &g...

...xing them with a special character. Avoiding > characters already used in some fashion (i.e. “!” for metadata and “#” for > attributes), I initially have chosen “^”. Open to suggestions > though.Consider the following example:extern void foo();int X;int bar() { > foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int > main() { barAlias(); return bar();}The proposed format has one entry per > ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks > like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = gv: {guid: > 188166723...

...er. Avoiding >>> characters already used in some fashion (i.e. “!” for metadata and “#” for >>> attributes), I initially have chosen “^”. Open to suggestions >>> though.Consider the following example:extern void foo();int X;int bar() { >>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>> main() { barAlias(); return bar();}The proposed format has one entry per >>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>> like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = g...

...;>>> characters already used in some fashion (i.e. “!” for metadata and “#” for >>>> attributes), I initially have chosen “^”. Open to suggestions >>>> though.Consider the following example:extern void foo();int X;int bar() { >>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>> like:^0 = module: {path: testA.o, hash: 54871973070456...

...xing them with a special character. Avoiding > characters already used in some fashion (i.e. “!” for metadata and “#” for > attributes), I initially have chosen “^”. Open to suggestions > though.Consider the following example:extern void foo();int X;int bar() { > foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int > main() { barAlias(); return bar();}The proposed format has one entry per > ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks > like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = gv: {guid: > 188166723...

...special character. Avoiding >> characters already used in some fashion (i.e. “!” for metadata and “#” for >> attributes), I initially have chosen “^”. Open to suggestions >> though.Consider the following example:extern void foo();int X;int bar() { >> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >> main() { barAlias(); return bar();}The proposed format has one entry per >> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >> like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = gv: {guid: &g...

...gh. Is there any reason or downside for just using metadata for summary? We can just stream summary related metadata into summary block in bitcode. > > Consider the following example: > > extern void foo(); > int X; > int bar() { > foo(); > return X; > } > void barAlias() __attribute__ ((alias ("bar"))); > int main() { > barAlias(); > return bar(); > } > > The proposed format has one entry per ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks like: > > ^0 = module: {path: testA.o, hash: 54871973070456662...

...xing them with a special character. Avoiding > characters already used in some fashion (i.e. “!” for metadata and “#” for > attributes), I initially have chosen “^”. Open to suggestions > though.Consider the following example:extern void foo();int X;int bar() { > foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int > main() { barAlias(); return bar();}The proposed format has one entry per > ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks > like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = gv: {guid: > 188166723...

...er. Avoiding >>> characters already used in some fashion (i.e. “!” for metadata and “#” for >>> attributes), I initially have chosen “^”. Open to suggestions >>> though.Consider the following example:extern void foo();int X;int bar() { >>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>> main() { barAlias(); return bar();}The proposed format has one entry per >>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>> like:^0 = module: {path: testA.o, hash: 5487197307045666224}^1 = g...

...;>>> characters already used in some fashion (i.e. “!” for metadata and “#” for >>>> attributes), I initially have chosen “^”. Open to suggestions >>>> though.Consider the following example:extern void foo();int X;int bar() { >>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>> like:^0 = module: {path: testA.o, hash: 54871973070456...

...already used in some fashion (i.e. “!” for metadata and “#” for >>>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>>> like:^0 = module: {path: testA...

...; characters already used in some fashion (i.e. “!” for metadata and “#” for >>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>> like:^0 = module: {path: testA.o, hash: 54...

...d in some fashion (i.e. “!” for metadata and “#” for >>>>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>>>> like:^0 = module:...

...“!” for metadata and “#” for >>>>>>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>>>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>>>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>>>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>>>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>>>>&gt...

...shion (i.e. “!” for metadata and “#” for >>>>>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>>>>> like:^...

...data and “#” for >>>>>>>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>>>>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>>>>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>>>>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>>>>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>>&gt...

...hion (i.e. “!” for metadata and “#” for attributes), I initially have chosen “^”. Open to suggestions though. >> >> Consider the following example: >> >> extern void foo(); >> int X; >> int bar() { >> foo(); >> return X; >> } >> void barAlias() __attribute__ ((alias ("bar"))); >> int main() { >> barAlias(); >> return bar(); >> } >> >> The proposed format has one entry per ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks like: >> >> ^0 = module: {path:...

...ding characters already used in some fashion (i.e. “!” for metadata and “#” for attributes), I initially have chosen “^”. Open to suggestions though. > > Consider the following example: > > extern void foo(); > int X; > int bar() { > foo(); > return X; > } > void barAlias() __attribute__ ((alias ("bar"))); > int main() { > barAlias(); > return bar(); > } > > The proposed format has one entry per ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks like: > > ^0 = module: {path: testA.o, hash: 54871973070456662...

...shion (i.e. “!” for metadata and “#” for >>>>>>>> attributes), I initially have chosen “^”. Open to suggestions >>>>>>>> though.Consider the following example:extern void foo();int X;int bar() { >>>>>>>> foo(); return X;}void barAlias() __attribute__ ((alias ("bar")));int >>>>>>>> main() { barAlias(); return bar();}The proposed format has one entry per >>>>>>>> ModulePathStringTable entry and one per GlobalValueMap/GUID, and looks >>>>>>>> like:^...