Displaying 3 results from an estimated 3 matches for "didescriptorref".
2014 Jul 21
2
[LLVMdev] LTO type uniquing: ODR assertion failure
...tadata !124, metadata !575, metadata !"_ZTS13SpuPacketType",
> metadata !582, metadata !212, metadata !128, metadata !584}
>
> And treat the field {metadata !"_ZTS13SpuPacketType"} as DITypeRef.
>
> -------------------------------------------------
> If we have DIDescriptorRef and all elements currently inside DIArray are
> DIDescirptors, we can make DIArray an array of DIDescriptorRef.
> I don't think it is a good idea to add DIDescriptorRef (it makes our types
> loose) and am not sure about the 2nd condition.
>
> So I proposed to add DITypeArray (or...
2014 Jul 21
4
[LLVMdev] LTO type uniquing: ODR assertion failure
...acketType",
>> > metadata !582, metadata !212, metadata !128, metadata !584}
>> >
>> > And treat the field {metadata !"_ZTS13SpuPacketType"} as DITypeRef.
>> >
>> > -------------------------------------------------
>> > If we have DIDescriptorRef and all elements currently inside DIArray are
>> > DIDescirptors, we can make DIArray an array of DIDescriptorRef.
>> > I don't think it is a good idea to add DIDescriptorRef (it makes our
>> > types
>> > loose) and am not sure about the 2nd condition.
>&g...
2014 Jul 21
2
[LLVMdev] LTO type uniquing: ODR assertion failure
On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>
>> We still have access to types via MDNodes directly and the assertion that
>> assumes all accesses to DITypes are accessing the resolved DIType will fire
>>
>> i.e