Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
	 nd <nd@arm.com>
Subject: Re: [PATCH] AArch64: Allow additional sizes in prologue
Date: Mon, 05 Aug 2019 17:43:00 -0000	[thread overview]
Message-ID: <8736ifcxu8.fsf@tromey.com> (raw)
In-Reply-To: <20190805124152.26127-1-alan.hayward@arm.com> (Alan Hayward's	message of "Mon, 5 Aug 2019 12:41:55 +0000")

>>>>> "Alan" == Alan Hayward <Alan.Hayward@arm.com> writes:

Alan> When saving registers to the stack at the start of a function, not all state
Alan> needs to be saved. For example, only the first 64bits of float registers need
Alan> saving.  However, a program may choose to store extra state if it wishes,
Alan> there is nothing preventing it doing so.

Alan> The aarch64_analyze_prologue will error if it detects extra state being
Alan> stored.  Relex this restriction.

I don't know anything about AArch64, so I can't really comment on the
content of the patch, but I did happen to see a nit:

Alan>  	  stack.store (pv_add_constant (regs[rn],
Alan>  					inst.operands[1].addr.offset.imm),
Alan> -		       is64 ? 8 : 4, regs[rt]);
Alan> +					size, regs[rt]);

...this addition looked mis-indented to me.

Tom


       reply	other threads:[~2019-08-05 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190805124152.26127-1-alan.hayward@arm.com>
2019-08-05 17:43 ` Tom Tromey [this message]
2019-08-06  8:58   ` Alan Hayward
2019-08-06  9:56     ` Richard Earnshaw (lists)
2019-08-06 12:18       ` Alan Hayward
2019-08-14 15:03         ` Alan Hayward
2019-08-06 13:52     ` Tom Tromey

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=8736ifcxu8.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.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