Displaying 20 results from an estimated 20 matches for "regmaskbits".
2016 May 11
3
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...true));
else
addFastRegAlloc(createRegAllocPass(false));
// Run post-ra passes.
addPostRegAlloc();
// Adding a new pass here which keeps register mask information across
function calls.
.
.
.
}
But this also requires current register allocators to use this information
in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static
across calls. I mean I am not clear for how to propagate static info to
Intra-procedural Register allocators (if possible without disturbing their
code )
I think this also applies in someway to Mehdi Amini's idea to keep a
ModulePass for bookkeeping bu...
2016 May 18
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...e));
>
> // Run post-ra passes.
> addPostRegAlloc();
> // Adding a new pass here which keeps register mask information across
> function calls.
> .
> .
> .
> }
>
> But this also requires current register allocators to use this information
> in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static
> across calls. I mean I am not clear for how to propagate static info to
> Intra-procedural Register allocators (if possible without disturbing their
> code )
>
> First, my hope is that we won't need to change the register allocators, as...
2016 May 18
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...>> addPostRegAlloc();
>> // Adding a new pass here which keeps register mask information across
>> function calls.
>> .
>> .
>> .
>> }
>>
>> But this also requires current register allocators to use this
>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>> not static across calls. I mean I am not clear for how to propagate static
>> info to Intra-procedural Register allocators (if possible without
>> disturbing their code )
>>
>> First, my hope is that we won't need to change the reg...
2016 May 18
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...post-ra passes.
>> addPostRegAlloc();
>> // Adding a new pass here which keeps register mask information across function calls.
>> .
>> .
>> .
>> }
>>
>> But this also requires current register allocators to use this information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static across calls. I mean I am not clear for how to propagate static info to Intra-procedural Register allocators (if possible without disturbing their code )
>> First, my hope is that we won't need to change the register allocators, as such, in order...
2016 May 24
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...t;> // Adding a new pass here which keeps register mask information across
>>> function calls.
>>> .
>>> .
>>> .
>>> }
>>>
>>> But this also requires current register allocators to use this
>>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>>> not static across calls. I mean I am not clear for how to propagate static
>>> info to Intra-procedural Register allocators (if possible without
>>> disturbing their code )
>>>
>>> First, my hope is that we won't ne...
2016 May 24
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...gt; > > >
> > > > >
> > > >
> > >
> >
>
> > > > > > > But this also requires current register allocators to use
> > > > > > > this
> > > > > > > information in someway because RegMaskBits in
> > > > > > > LiveIntervalAnalysis.cpp is not static across calls. I
> > > > > > > mean
> > > > > > > I
> > > > > > > am
> > > > > > > not
> > > > > > > clear for how to...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...which keeps register mask information across
>>>> function calls.
>>>> .
>>>> .
>>>> .
>>>> }
>>>>
>>>> But this also requires current register allocators to use this
>>>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>>>> not static across calls. I mean I am not clear for how to propagate static
>>>> info to Intra-procedural Register allocators (if possible without
>>>> disturbing their code )
>>>>
>>>> First, my hope is...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...; >
> >
>
> > > > > > > > > But this also requires current register allocators to
> > > > > > > > > use
> > > > > > > > > this
> > > > > > > > > information in someway because RegMaskBits in
> > > > > > > > > LiveIntervalAnalysis.cpp is not static across calls.
> > > > > > > > > I
> > > > > > > > > mean
> > > > > > > > > I
> > > > > > > > > am
> &...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...mation across
>>>>> function calls.
>>>>> .
>>>>> .
>>>>> .
>>>>> }
>>>>>
>>>>> But this also requires current register allocators to use this
>>>>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>>>>> not static across calls. I mean I am not clear for how to propagate static
>>>>> info to Intra-procedural Register allocators (if possible without
>>>>> disturbing their code )
>>>>>
>>>>>...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...across function calls.
>>>>>> .
>>>>>> .
>>>>>> .
>>>>>> }
>>>>>>
>>>>>> But this also requires current register allocators to use this
>>>>>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>>>>>> not static across calls. I mean I am not clear for how to propagate static
>>>>>> info to Intra-procedural Register allocators (if possible without
>>>>>> disturbing their code )
>>>>>>
>...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...ass(false));
>
> // Run post-ra passes.
> addPostRegAlloc();
> // Adding a new pass here which keeps register mask information across function calls.
> .
> .
> .
> }
>
> But this also requires current register allocators to use this information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static across calls. I mean I am not clear for how to propagate static info to Intra-procedural Register allocators (if possible without disturbing their code )
> First, my hope is that we won't need to change the register allocators, as such, in order to m...
2016 May 25
3
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...post-ra passes.
>> addPostRegAlloc();
>> // Adding a new pass here which keeps register mask information across function calls.
>> .
>> .
>> .
>> }
>>
>> But this also requires current register allocators to use this information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static across calls. I mean I am not clear for how to propagate static info to Intra-procedural Register allocators (if possible without disturbing their code )
>> First, my hope is that we won't need to change the register allocators, as such, in order...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...gt;>>>>> .
>>>>>>> .
>>>>>>> .
>>>>>>> }
>>>>>>>
>>>>>>> But this also requires current register allocators to use this
>>>>>>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>>>>>>> not static across calls. I mean I am not clear for how to propagate static
>>>>>>> info to Intra-procedural Register allocators (if possible without
>>>>>>> disturbing their code )
>>>>...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...t;>>>> .
>>>>>>>>>>> .
>>>>>>>>>>> }
>>>>>>>>>>>
>>>>>>>>>>> But this also requires current register allocators to use this information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static across calls. I mean I am not clear for how to propagate static info to Intra-procedural Register allocators (if possible without disturbing their code )
>>>>>>>>>>> First, my hope is that we won't need to change the reg...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
....
>>>>>>>> .
>>>>>>>> .
>>>>>>>> }
>>>>>>>>
>>>>>>>> But this also requires current register allocators to use this
>>>>>>>> information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is
>>>>>>>> not static across calls. I mean I am not clear for how to propagate static
>>>>>>>> info to Intra-procedural Register allocators (if possible without
>>>>>>>> disturbing their code )
>...
2016 May 11
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...ass(false));
>
> // Run post-ra passes.
> addPostRegAlloc();
> // Adding a new pass here which keeps register mask information across function calls.
> .
> .
> .
> }
>
> But this also requires current register allocators to use this information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static across calls. I mean I am not clear for how to propagate static info to Intra-procedural Register allocators (if possible without disturbing their code )
> First, my hope is that we won't need to change the register allocators, as such, in order to m...
2016 May 11
3
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...ass(false));
>
> // Run post-ra passes.
> addPostRegAlloc();
> // Adding a new pass here which keeps register mask information across function calls.
> .
> .
> .
> }
>
> But this also requires current register allocators to use this information in someway because RegMaskBits in LiveIntervalAnalysis.cpp is not static across calls. I mean I am not clear for how to propagate static info to Intra-procedural Register allocators (if possible without disturbing their code )
> First, my hope is that we won't need to change the register allocators, as such, in order to m...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...> use
> > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > information in someway because
> > > > > > > > > > > > > > > > > RegMaskBits
> > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > LiveIntervalAnalysis.cpp is not
> > > > > > > > > > > > > > > > > static
&g...
2016 May 11
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...;
> > > > > > }
> > > > >
> > > >
> > >
> >
>
> > > > > > But this also requires current register allocators to use
> > > > > > this
> > > > > > information in someway because RegMaskBits in
> > > > > > LiveIntervalAnalysis.cpp is not static across calls. I mean
> > > > > > I
> > > > > > am
> > > > > > not
> > > > > > clear for how to propagate static info to Intra-procedural
> > > >...
2016 May 11
4
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
> On May 10, 2016, at 6:06 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>
>
>
> From: "vivek pandya" <vivekvpandya at gmail.com>
> To: "llvm-dev" <llvm-dev at lists.llvm.org>, "Tim Amini Golling" <mehdi.amini at apple.com>, "Hal Finkel" <hfinkel at anl.gov>
> Cc: "Quentin Colombet" <qcolombet