From: James Greenhalgh <james.greenhalgh@arm.com>
To: Jiong Wang <jiong.wang@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [AArch64] PR 63521. define REG_ALLOC_ORDER/HONOR_REG_ALLOC_ORDER
Date: Wed, 22 Jul 2015 11:37:00 -0000 [thread overview]
Message-ID: <20150722112203.GA17314@arm.com> (raw)
In-Reply-To: <n998ucjwgk1.fsf@arm.com>
On Wed, May 20, 2015 at 01:35:41PM +0100, Jiong Wang wrote:
> Current IRA still use both target macros in a few places.
>
> Tell IRA to use the order we defined rather than with it's own cost
> calculation. Allocate caller saved first, then callee saved.
>
> This is especially useful for LR/x30, as it's free to allocate and is
> pure caller saved when used in leaf function.
>
> Haven't noticed significant impact on benchmarks, but by grepping some
> keywords like "Spilling", "Push.*spill" etc in ira rtl dump, the number
> is smaller.
>
> OK for trunk?
OK, sorry for the delay.
It might be mail client mangling, but please check that the trailing slashes
line up in the version that gets committed.
Thanks,
James
> 2015-05-19 Jiong. Wang <jiong.wang@arm.com>
>
> gcc/
> PR 63521
> * config/aarch64/aarch64.h (REG_ALLOC_ORDER): Define.
> (HONOR_REG_ALLOC_ORDER): Define.
>
> diff --git a/gcc/config/aarch64/aarch64.h b/gcc/config/aarch64/aarch64.h
> index bf59e40..0acdf10 100644
> --- a/gcc/config/aarch64/aarch64.h
> +++ b/gcc/config/aarch64/aarch64.h
> @@ -337,6 +337,31 @@ extern unsigned long aarch64_tune_flags;
> V_ALIASES(28), V_ALIASES(29), V_ALIASES(30), V_ALIASES(31) \
> }
>
> +#define REG_ALLOC_ORDER \
> +{ \
> + /* Reverse order for argument registers. */ \
> + 7, 6, 5, 4, 3, 2, 1, 0, \
> + /* Other caller-saved registers. */ \
> + 8, 9, 10, 11, 12, 13, 14, 15, \
> + 16, 17, 18, 30, \
> + /* Callee-saved registers. */ \
> + 19, 20, 21, 22, 23, 24, 25, 26, \
> + 27, 28, \
> + /* All other registers. */ \
> + 29, 31, \
> + /* Reverse order for argument vregisters. */ \
> + 39, 38, 37, 36, 35, 34, 33, 32, \
> + /* Other caller-saved vregisters. */ \
> + 48, 49, 50, 51, 52, 53, 54, 55, \
> + 56, 57, 58, 59, 60, 61, 62, 63, \
> + /* Callee-saved vregisters. */ \
> + 40, 41, 42, 43, 44, 45, 46, 47, \
> + /* Other pseudo registers. */ \
> + 64, 65, 66 \
> +}
> +
> +#define HONOR_REG_ALLOC_ORDER 1
> +
> /* Say that the epilogue uses the return address register. Note that
> in the case of sibcalls, the values "used by the epilogue" are
> considered live at the start of the called function. */
next prev parent reply other threads:[~2015-07-22 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 13:02 Jiong Wang
2015-07-22 11:01 ` [AArch64] PR63521 Define REG_ALLOC_ORDER/HONOR_REG_ALLOC_ORDER Jiong Wang
2015-07-22 11:37 ` James Greenhalgh [this message]
2015-07-24 9:11 ` [Revert][AArch64] PR 63521 " Jiong Wang
2015-07-25 20:02 ` Andrew Pinski
2015-07-27 9:52 ` Jiong Wang
2015-07-27 10:25 ` pinskia
2015-07-27 10:44 ` James Greenhalgh
2016-08-03 6:18 ` Andrew Pinski
2016-08-05 17:02 ` Jiong Wang
2016-08-08 17:05 ` Jiong Wang
2016-08-10 16:49 ` Vladimir N Makarov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150722112203.GA17314@arm.com \
--to=james.greenhalgh@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).