Displaying 5 results from an estimated 5 matches for "jsctype".
2013 Oct 11
2
[LLVMdev] Request for comments: TBAA on call
...r option of trying to generate some fake set of heaps that accurately represent the conflicts in both is, well, difficult :)
> _______________________________________________
JSC is able to make better use of the original TBAA design by encoding the access path within the type itself. Roughly:
JSCType->Class->Field/Index
This is what we're doing with C++ struct-path TBAA now, but simpler because only one access path is legal.
JSC does need a hierarchical representation which makes TBAA a perfect fit.
The only decision point to make now is whether to allow current TBAA to apply to ca...
2013 Oct 11
0
[LLVMdev] Request for comments: TBAA on call
...me fake set of heaps that
> accurately represent the conflicts in both is, well, difficult :)
> _______________________________________________
>
>
> JSC is able to make better use of the original TBAA design by encoding the
> access path within the type itself. Roughly:
>
> JSCType->Class->Field/Index
>
> This is what we're doing with C++ struct-path TBAA now, but simpler
> because only one access path is legal.
>
> JSC does need a hierarchical representation which makes TBAA a perfect fit.
>
> The only decision point to make now is whether to a...
2013 Oct 11
1
[LLVMdev] Request for comments: TBAA on call
...t; accurately represent the conflicts in both is, well, difficult :)
>> _______________________________________________
>>
>>
>> JSC is able to make better use of the original TBAA design by encoding
>> the access path within the type itself. Roughly:
>>
>> JSCType->Class->Field/Index
>>
>> This is what we're doing with C++ struct-path TBAA now, but simpler
>> because only one access path is legal.
>>
>> JSC does need a hierarchical representation which makes TBAA a perfect
>> fit.
>>
>> The only decis...
2013 Oct 11
0
[LLVMdev] Request for comments: TBAA on call
On Thu, Oct 10, 2013 at 10:34 AM, Chris Lattner <clattner at apple.com> wrote:
> On Oct 7, 2013, at 11:49 PM, Daniel Berlin <dberlin at dberlin.org> wrote:
>
>
>> Hence it’s more meaningful to reason about TBAA in terms of its semantics
>> rather than hypothesizing about how and why someone would produce it.
>>
>
> That would be great, but it's not
2013 Oct 10
4
[LLVMdev] Request for comments: TBAA on call
On Oct 7, 2013, at 11:49 PM, Daniel Berlin <dberlin at dberlin.org> wrote:
>
> Hence it’s more meaningful to reason about TBAA in terms of its semantics rather than hypothesizing about how and why someone would produce it.
>
> That would be great, but it's not what the langref says, nor does it match up with the name of the thing you are creating, nor does it necessarily