On 15/05/14 00:22, 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?

target hooks like aarch64_register_move_cost doesn’t handle CORE_REGS. In addition, IRA cost calculation also has logics like make common class biggest of best and alternate; this might get confused with this.

Attached RFC patch removes it. regression tested for aarch64-none-linux-gnu on qemu-aarch64 with now new regression. Is this OK ?

Patches for gcc need to be sent to gcc-patches...

R.

Thanks, Kugan

gcc/

2014-05-14 Kugan Vivekanandarajah kuganv@linaro.org

• config/aarch64/aarch64.c (aarch64_regno_regclass) : Change CORE_REGS

to GENERAL_REGS. (aarch64_secondary_reload) : LikeWise. (aarch64_class_max_nregs) : Remove CORE_REGS.

• config/aarch64/aarch64.h (enum reg_class) : Remove CORE_REGS.

(REG_CLASS_NAMES) : Likewise. (REG_CLASS_CONTENTS) : LikeWise. (INDEX_REG_CLASS) : Change CORE_REGS to GENERAL_REGS.