Displaying 6 results from an estimated 6 matches for "aarach64".
2017 Oct 27
2
Less aggressive on the first allocation of CSR if detecting an early exit
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 block. So CSR
spills/reloads are executed even when the early exit block is taken.
int getI(int i);
int foo(int *P, int i) {
if (i>0)
return P[i];
i = getI(i);
return P[i];...
2017 Oct 30
2
Less aggressive on the first allocation of CSR if detecting an early exit
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 block.
>> So CSR spills/reloads are executed even when the early exit block is
>> taken.
>>
>> int getI(int i);
>>
>> int foo(int *P, int 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 block.
>>>> So CSR spills/reloads are executed even when the early exit block is
>>>> taken.
>>>>
>>>> int getI(int i);
>>>>
&...
2017 Nov 10
2
Less aggressive on the first allocation of CSR if detecting an early exit
...llvm.org> wrote:
>
>> 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 block.
>> So CSR spills/reloads are executed even when the early exit block is
>> taken.
>>
>> int getI(int i);
>>
>> int foo(int *P, int i) {
>&g...
2017 Nov 16
2
Less aggressive on the first allocation of CSR if detecting an early exit
...vm-dev at lists.llvm.org> wrote:
>> 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 block.
>> So CSR spills/reloads are executed even when the early exit block is
>> taken.
>> int getI(int i);
>> int foo(int *P, int i) {
>> if (i>0)
>&...
2017 Nov 17
2
Less aggressive on the first allocation of CSR if detecting an early exit
...vm-dev at lists.llvm.org> wrote:
>> 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 block.
>> So CSR spills/reloads are executed even when the early exit block is
>> taken.
>> int getI(int i);
>> int foo(int *P, int i) {
>> if (i>0)
>&...