public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>,
	Richard Earnshaw	<Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][AArch64] Simplify aarch64_can_eliminate
Date: Tue, 07 Nov 2017 17:27:00 -0000	[thread overview]
Message-ID: <20171107171127.GB30919@arm.com> (raw)
In-Reply-To: <DB6PR0801MB2053154CE220461410BD4DF5838D0@DB6PR0801MB2053.eurprd08.prod.outlook.com>

On Tue, Aug 15, 2017 at 05:25:06PM +0100, Wilco Dijkstra wrote:
> 
> ping
> 
> 
> From: Wilco Dijkstra
> Sent: 07 August 2017 15:13
> To: GCC Patches; James Greenhalgh
> Cc: nd; Richard Earnshaw
> Subject: [PATCH][AArch64] Simplify aarch64_can_eliminate
>     
> Simplify aarch64_can_eliminate - if we need a frame pointer, we must
> eliminate to HARD_FRAME_POINTER_REGNUM.  Rather than hardcoding all
> combinations from the ELIMINABLE_REGS list, just do the correct check.
> 
> ChangeLog:
> 2017-08-07  Wilco Dijkstra  <wdijkstr@arm.com>
> 
>     gcc/
>         * config/aarch64/aarch64.c (aarch64_can_eliminate): Simplify logic.
> --
> 
> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
> index 9463edf63ffe770062b4120fada090e20c93a269..fbb4244cb58d2a25203aa27342c2f7988c30bd98 100644
> --- a/gcc/config/aarch64/aarch64.c
> +++ b/gcc/config/aarch64/aarch64.c
> @@ -5858,26 +5858,12 @@ aarch64_secondary_reload (bool in_p ATTRIBUTE_UNUSED, rtx x,
>  }
>  
>  static bool
> -aarch64_can_eliminate (const int from, const int to)
> +aarch64_can_eliminate (const int from ATTRIBUTE_UNUSED, const int to)
>  {
> -  /* If we need a frame pointer, we must eliminate FRAME_POINTER_REGNUM into
> -     HARD_FRAME_POINTER_REGNUM and not into STACK_POINTER_REGNUM.  */
> -
> +  /* If we need a frame pointer, ARG_POINTER_REGNUM and FRAME_POINTER_REGNUM
> +     can only eliminate to HARD_FRAME_POINTER_REGNUM.  */

Please add an assert in here,

  (from == ARG_POINTER_REGNUM || from == FRAME_POINTER_REGNUM)

Otherwise, OK (please test this against a recent trunk).

Reviewed-By: James Greenhalgh <james.greenhalgh@arm.com>

Thanks,
James

>    if (frame_pointer_needed)
> -    {
> -      if (from == ARG_POINTER_REGNUM && to == HARD_FRAME_POINTER_REGNUM)
> -       return true;
> -      if (from == ARG_POINTER_REGNUM && to == STACK_POINTER_REGNUM)
> -       return false;
> -      if (from == FRAME_POINTER_REGNUM && to == STACK_POINTER_REGNUM
> -         && !cfun->calls_alloca)
> -       return true;
> -      if (from == FRAME_POINTER_REGNUM && to == HARD_FRAME_POINTER_REGNUM)
> -       return true;
> -
> -      return false;
> -    }
> -
> +    return to == HARD_FRAME_POINTER_REGNUM;
>    return true;
>  }    

      reply	other threads:[~2017-11-07 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 14:13 Wilco Dijkstra
2017-08-15 16:27 ` Wilco Dijkstra
2017-11-07 17:27   ` James Greenhalgh [this message]

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=20171107171127.GB30919@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@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).