Displaying 4 results from an estimated 4 matches for "regallc".
Did you mean:
regalloc
2017 Nov 10
2
Less aggressive on the first allocation of CSR if detecting an early exit
...ion would give us what we want, but there may be
> [obvious] counter-examples I haven't thought of.
>
Thanks Nemanja for sharing your idea. I think this might cover the case
I was targeting, and we may not need to be limited only in the entry
block.
However, I bit worry if this cause RegAllc to slow in allocating CSRs.
What if we have a call-site in the early exit path and no call-site in
all other blocks. Then, conservative allocation of CSRs might not be a
good choice if the reg pressure is high in the all other blocks. As our
first step, would it make sense to limit this only...
2017 Nov 16
2
Less aggressive on the first allocation of CSR if detecting an early exit
...y be
>>> [obvious] counter-examples I haven't thought of.
>>
>> Thanks Nemanja for sharing your idea. I think this might cover the
>> case I was targeting, and we may not need to be limited only in the
>> entry block.
>> However, I bit worry if this cause RegAllc to slow in allocating
>> CSRs. What if we have a call-site in the early exit path and no
>> call-site in all other blocks. Then, conservative allocation of CSRs
>> might not be a good choice if the reg pressure is high in the all
>> other blocks. As our first step, would i...
2017 Nov 17
2
Less aggressive on the first allocation of CSR if detecting an early exit
...re
>> may be
>> [obvious] counter-examples I haven't thought of.
>> Thanks Nemanja for sharing your idea. I think this might cover the
>> case I was targeting, and we may not need to be limited only in the
>> entry block.
>> However, I bit worry if this cause RegAllc to slow in allocating
>> CSRs. What if we have a call-site in the early exit path and no
>> call-site in all other blocks. Then, conservative allocation of CSRs
>> might not be a good choice if the reg pressure is high in the all
>> other blocks. As our first step, would i...
2017 Oct 31
2
Less aggressive on the first allocation of CSR if detecting an early exit
On 2017-10-30 21:20, Hal Finkel wrote:
> On 10/30/2017 12:20 PM, junbuml at codeaurora.org wrote:
>> On 2017-10-27 19:50, Hal Finkel wrote:
>>> On 10/27/2017 03:32 PM, Jun Lim via llvm-dev wrote:
>>>
>>>> When compiling C code below for AArach64, I saw that shrink-wrapping
>>>> didn't happen due to the very early uses of CSRs in the entry