search for: baralia

Displaying 20 results from an estimated 26 matches for "baralia".

Did you mean: baralias
2018 Apr 24
8
RFC: LLVM Assembly format for ThinLTO Summary
...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...
2018 May 03
2
RFC: LLVM Assembly format for ThinLTO Summary
...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: &...
2018 May 03
0
RFC: LLVM Assembly format for ThinLTO Summary
...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: > 18816672...
2018 May 03
0
RFC: LLVM Assembly format for ThinLTO Summary
...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 =...
2018 May 03
1
RFC: LLVM Assembly format for ThinLTO Summary
...;>>> 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: 5487197307045...
2018 Apr 25
0
RFC: LLVM Assembly format for ThinLTO Summary
...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: > 18816672...
2018 Apr 30
2
RFC: LLVM Assembly format for ThinLTO Summary
...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: &...
2018 Apr 25
0
RFC: LLVM Assembly format for ThinLTO Summary
...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: 5487197307045666...
2018 Apr 30
0
RFC: LLVM Assembly format for ThinLTO Summary
...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: > 18816672...
2018 Apr 30
0
RFC: LLVM Assembly format for ThinLTO Summary
...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 =...
2018 May 01
3
RFC: LLVM Assembly format for ThinLTO Summary
...;>>> 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: 5487197307045...
2018 May 01
3
RFC: LLVM Assembly format for ThinLTO Summary
...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: test...
2018 May 01
0
RFC: LLVM Assembly format for ThinLTO Summary
...; 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: 5...
2018 May 01
0
RFC: LLVM Assembly format for ThinLTO Summary
...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:...
2018 May 03
0
RFC: LLVM Assembly format for ThinLTO Summary
...“!” 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 >>>>>>>&g...
2018 May 03
3
RFC: LLVM Assembly format for ThinLTO Summary
...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:...
2018 May 03
4
RFC: LLVM Assembly format for ThinLTO Summary
...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 >>>>>&g...
2018 May 03
1
RFC: LLVM Assembly format for ThinLTO Summary
...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:...
2018 May 03
3
RFC: LLVM Assembly format for ThinLTO Summary
...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: 5487197307045666...
2018 May 03
0
RFC: LLVM Assembly format for ThinLTO Summary
...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:...