search for: _ztifvve

Displaying 4 results from an estimated 4 matches for "_ztifvve".

2013 Jul 18
0
[LLVMdev] Proposal: function prefix data
...combined with my earlier symbol > offset proposal [2] as applied to functions. However, this is outside > the scope of the current proposal. > > Example: > > %0 = type <{ i32, i8* }> > > define void @f() prefix %0 <{ i32 1413876459, i8* bitcast ({ i8*, i8* }* > @_ZTIFvvE to i8*) }> { > ret void > } > > This is an example of something that UBSan might generate on an > x86_64 machine. It consists of a signature of 4 bytes followed by a > pointer to the RTTI data for the type 'void ()'. The signature when > laid out as a little endi...
2013 Jul 18
6
[LLVMdev] Proposal: function prefix data
.... This requirement could be relaxed when combined with my earlier symbol offset proposal [2] as applied to functions. However, this is outside the scope of the current proposal. Example: %0 = type <{ i32, i8* }> define void @f() prefix %0 <{ i32 1413876459, i8* bitcast ({ i8*, i8* }* @_ZTIFvvE to i8*) }> { ret void } This is an example of something that UBSan might generate on an x86_64 machine. It consists of a signature of 4 bytes followed by a pointer to the RTTI data for the type 'void ()'. The signature when laid out as a little endian 32-bit integer decodes to the i...
2013 Jul 18
2
[LLVMdev] Proposal: function prefix data
...set proposal [2] as applied to functions. However, this is outside > > the scope of the current proposal. > > > > Example: > > > > %0 = type <{ i32, i8* }> > > > > define void @f() prefix %0 <{ i32 1413876459, i8* bitcast ({ i8*, i8* }* > > @_ZTIFvvE to i8*) }> { > > ret void > > } > > > > This is an example of something that UBSan might generate on an > > x86_64 machine. It consists of a signature of 4 bytes followed by a > > pointer to the RTTI data for the type 'void ()'. The signature when...
2013 Jul 18
0
[LLVMdev] Proposal: function prefix data
...wever, this is outside > > > the scope of the current proposal. > > > > > > Example: > > > > > > %0 = type <{ i32, i8* }> > > > > > > define void @f() prefix %0 <{ i32 1413876459, i8* bitcast ({ i8*, i8* > }* > > > @_ZTIFvvE to i8*) }> { > > > ret void > > > } > > > > > > This is an example of something that UBSan might generate on an > > > x86_64 machine. It consists of a signature of 4 bytes followed by a > > > pointer to the RTTI data for the type 'void...