search for: typeid3

...!type !0, !type !2 @b = constant [63 x i32] zeroinitializer, !type !0, !type !1 @c = constant i32 3, !type !1, !type !2 @d = constant [2 x i32] [i32 4, i32 5], !type !3 !0 = !{i32 0, !"typeid1"} !3 = !{i32 4, !"typeid1"} !1 = !{i32 0, !"typeid2"} !2 = !{i32 0, !"typeid3"} define i1 @baz(i32* %p) { %x = call i1 @llvm.type.test(i8* %pi8, metadata !"typeid3") ret i1 %x } Here is the IR after the LowerTypeTests pass has run. I've marked the places where we use a constant value: define i1 @baz(i32* %p) { %pi8 = bitcast i32* %p to i8* %1 =...

...[63 x i32] zeroinitializer, !type !0, !type !1 > @c = constant i32 3, !type !1, !type !2 > @d = constant [2 x i32] [i32 4, i32 5], !type !3 > > !0 = !{i32 0, !"typeid1"} > !3 = !{i32 4, !"typeid1"} > !1 = !{i32 0, !"typeid2"} > !2 = !{i32 0, !"typeid3"} > > define i1 @baz(i32* %p) { > %x = call i1 @llvm.type.test(i8* %pi8, metadata !"typeid3") > ret i1 %x > } > > Here is the IR after the LowerTypeTests pass has run. I've marked the > places where we use a constant value: > > define i1 @baz(i32...

...t; that maps GUID -> identifier? >>> >> >> I mean that you could represent this with something like: >> >> ^typeids = {^1, ^2, ^3} >> ^1 = typeid: {identifier: typeid1, ...} >> ^2 = typeid: {identifier: typeid2, ...} >> ^3 = typeid: {identifier: typeid3, ...} >> >> There's no need to store the GUIDs here because they can be computed from >> the type identifiers. The GUIDs would only be stored in the typeTests >> (etc.) fields in each function summary. >> > > I suppose we don't need to store the GUIDs at...

...create a top-level entity >> that maps GUID -> identifier? >> > > I mean that you could represent this with something like: > > ^typeids = {^1, ^2, ^3} > ^1 = typeid: {identifier: typeid1, ...} > ^2 = typeid: {identifier: typeid2, ...} > ^3 = typeid: {identifier: typeid3, ...} > > There's no need to store the GUIDs here because they can be computed from > the type identifiers. The GUIDs would only be stored in the typeTests > (etc.) fields in each function summary. > I suppose we don't need to store the GUIDs at the top level in the in-memor...

...er? >>>> >>> >>> I mean that you could represent this with something like: >>> >>> ^typeids = {^1, ^2, ^3} >>> ^1 = typeid: {identifier: typeid1, ...} >>> ^2 = typeid: {identifier: typeid2, ...} >>> ^3 = typeid: {identifier: typeid3, ...} >>> >>> There's no need to store the GUIDs here because they can be computed >>> from the type identifiers. The GUIDs would only be stored in the typeTests >>> (etc.) fields in each function summary. >>> >> >> I suppose we don't...

...;>> >>>> I mean that you could represent this with something like: >>>> >>>> ^typeids = {^1, ^2, ^3} >>>> ^1 = typeid: {identifier: typeid1, ...} >>>> ^2 = typeid: {identifier: typeid2, ...} >>>> ^3 = typeid: {identifier: typeid3, ...} >>>> >>>> There's no need to store the GUIDs here because they can be computed >>>> from the type identifiers. The GUIDs would only be stored in the typeTests >>>> (etc.) fields in each function summary. >>>> >>> >&gt...

...ou could represent this with something like: >>>>>> >>>>>> ^typeids = {^1, ^2, ^3} >>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>> >>>>>> There's no need to store the GUIDs here because they can be computed >>>>>> from the type identifiers. The GUIDs would only be stored in the typeTests >>>>>> (etc.) fields in each function summary. >&...

...t;> I mean that you could represent this with something like: >>>>> >>>>> ^typeids = {^1, ^2, ^3} >>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>> >>>>> There's no need to store the GUIDs here because they can be computed >>>>> from the type identifiers. The GUIDs would only be stored in the typeTests >>>>> (etc.) fields in each function summary. >>>>>...

...his with something like: >>>>>>> >>>>>>> ^typeids = {^1, ^2, ^3} >>>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>>> >>>>>>> There's no need to store the GUIDs here because they can be computed >>>>>>> from the type identifiers. The GUIDs would only be stored in the typeTests >>>>>>> (etc.) fields in each functio...

...-level entity that maps GUID -> identifier? >> >> I mean that you could represent this with something like: >> >> ^typeids = {^1, ^2, ^3} >> ^1 = typeid: {identifier: typeid1, ...} >> ^2 = typeid: {identifier: typeid2, ...} >> ^3 = typeid: {identifier: typeid3, ...} >> >> There's no need to store the GUIDs here because they can be computed from the type identifiers. The GUIDs would only be stored in the typeTests (etc.) fields in each function summary. >> >> I suppose we don't need to store the GUIDs at the top level in...

...he compile step create a top-level entity that maps GUID -> identifier? > > I mean that you could represent this with something like: > > ^typeids = {^1, ^2, ^3} > ^1 = typeid: {identifier: typeid1, ...} > ^2 = typeid: {identifier: typeid2, ...} > ^3 = typeid: {identifier: typeid3, ...} > > There's no need to store the GUIDs here because they can be computed from the type identifiers. The GUIDs would only be stored in the typeTests (etc.) fields in each function summary. > > I suppose we don't need to store the GUIDs at the top level in the in-memory su...

...t;> I mean that you could represent this with something like: >>>>> >>>>> ^typeids = {^1, ^2, ^3} >>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>> >>>>> There's no need to store the GUIDs here because they can be computed >>>>> from the type identifiers. The GUIDs would only be stored in the typeTests >>>>> (etc.) fields in each function summary. >>>>>...

...;>>>>> >>>>>>>>> ^typeids = {^1, ^2, ^3} >>>>>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>>>>> >>>>>>>>> There's no need to store the GUIDs here because they can be >>>>>>>>> computed from the type identifiers. The GUIDs would only be stored in the >>>>>>>>> typeTes...

...;> >>>>>>>>>> ^typeids = {^1, ^2, ^3} >>>>>>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>>>>>> >>>>>>>>>> There's no need to store the GUIDs here because they can be >>>>>>>>>> computed from the type identifiers. The GUIDs would only be stored in the >>>>>>>>...

...;>>>>> >>>>>>>>> ^typeids = {^1, ^2, ^3} >>>>>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>>>>> >>>>>>>>> There's no need to store the GUIDs here because they can be >>>>>>>>> computed from the type identifiers. The GUIDs would only be stored in the >>>>>>>>> typeTes...

...onfirm, you mean during the compile step create a top-level entity > that maps GUID -> identifier? > I mean that you could represent this with something like: ^typeids = {^1, ^2, ^3} ^1 = typeid: {identifier: typeid1, ...} ^2 = typeid: {identifier: typeid2, ...} ^3 = typeid: {identifier: typeid3, ...} There's no need to store the GUIDs here because they can be computed from the type identifiers. The GUIDs would only be stored in the typeTests (etc.) fields in each function summary. Peter > > Thanks, > Teresa > > >> >> Peter >> >> >>> &...

...ike: >>>>>>>> >>>>>>>> ^typeids = {^1, ^2, ^3} >>>>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>>>> >>>>>>>> There's no need to store the GUIDs here because they can be >>>>>>>> computed from the type identifiers. The GUIDs would only be stored in the >>>>>>>> typeTests (etc.) fields...

...;> >>>>>>>>>> ^typeids = {^1, ^2, ^3} >>>>>>>>>> ^1 = typeid: {identifier: typeid1, ...} >>>>>>>>>> ^2 = typeid: {identifier: typeid2, ...} >>>>>>>>>> ^3 = typeid: {identifier: typeid3, ...} >>>>>>>>>> >>>>>>>>>> There's no need to store the GUIDs here because they can be >>>>>>>>>> computed from the type identifiers. The GUIDs would only be stored in the >>>>>>>>...

Hi Peter, Thanks for your comments, replies below. Teresa On Wed, Apr 25, 2018 at 2:08 PM Peter Collingbourne <peter at pcc.me.uk> wrote: > Hi Teresa, > > Thanks for sending this proposal out. > > I would again like to register my disagreement with the whole idea of > writing summaries in LLVM assembly format. In my view it is clear that this > is not the right