Displaying 3 results from an estimated 3 matches for "0xstuff".
2013 Nov 08
1
[LLVMdev] Proposal for safe-to-execute meta-data for heap accesses
...indirected object model (for example when implementing dynamic language heap accesses):
%object = inttoptr %value
%p1 = getelementptr %object, <things>
%p2 = load %p1 !notrap !{ @isObject, %value }
%p3 = getelementptr %p3, <more things>
%v = load %p3 !notrap !{ @hasShape, %object, 0xstuff } // 0xstuff will be a compile-time constant
I can’t think of any examples where you’d want to use safe-to-execute and where Hal’s rule won’t hold.
-Filip
>
> -Hal
>
>>
>>
>>
>>
>>
>> It's not clear how that is better than any of the other...
2013 Nov 08
0
[LLVMdev] Proposal for safe-to-execute meta-data for heap accesses
----- Original Message -----
>
>
>
>
>
> On Nov 8, 2013, at 1:13 AM, Chandler Carruth < chandlerc at google.com >
> wrote:
>
>
>
>
>
>
>
>
> On Thu, Nov 7, 2013 at 9:39 PM, Filip Pizlo < fpizlo at apple.com >
> wrote:
>
>
>
> NEW PROPOSAL
>
> The solution is to introduce meta-data that is explicit
2013 Nov 08
5
[LLVMdev] Proposal for safe-to-execute meta-data for heap accesses
> On Nov 8, 2013, at 1:13 AM, Chandler Carruth <chandlerc at google.com> wrote:
>
>
>> On Thu, Nov 7, 2013 at 9:39 PM, Filip Pizlo <fpizlo at apple.com> wrote:
>> NEW PROPOSAL
>>
>> The solution is to introduce meta-data that is explicit about how the safe-to-execute condition ought to be evaluated. Instead of an SSA use, we can have meta-data that