On 27 May 2014 23:27, Kugan wrote:
> Due to the cost changes in IRA, now part of the arguments(v0.d[1]) for
> multf3 ends up in stack. Reason for this us, in IRA, assign_hard_reg,
> while iterating for the cost for assigning register to reg:TI 99,
> allocates register 32 (FP register). Which I th
On 22/05/14 01:08, Marcus Shawcroft wrote:
> On 15 May 2014 01:10, Kugan wrote:
>>
>> Hi All,
>>
>> AAarch64 back-end defines GENERAL_REGS and CORE_REGS with the same set
>> of register. Is there any reason why we need this?
>
> Nope an artifact of the early evolution of AArch64. Long ago CORE_R
On 15 May 2014 01:10, Kugan wrote:
>
> Hi All,
>
> AAarch64 back-end defines GENERAL_REGS and CORE_REGS with the same set
> of register. Is there any reason why we need this?
Nope an artifact of the early evolution of AArch64. Long ago CORE_REGS
did not include SP. Your patch is fine, commit it.
Hi All,
AAarch64 back-end defines GENERAL_REGS and CORE_REGS with the same set
of register. Is there any reason why we need this?
target hooks like aarch64_register_move_cost doesnt handle CORE_REGS.
In addition, IRA cost calculation also has logics like make common class
biggest of best and al
