From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2 v2] [AArch64] Recognize STR instruction in prologue
Date: Thu, 01 Dec 2016 13:07:00 -0000 [thread overview]
Message-ID: <2b5ae431-5bfb-2adf-aafb-fa2cbda12619@redhat.com> (raw)
In-Reply-To: <1480591000-19457-2-git-send-email-yao.qi@linaro.org>
Hi Yao,
On 12/01/2016 11:16 AM, Yao Qi wrote:
> + else if ((inst.opcode->iclass == ldst_imm9 /* Signed immediate. */
> + || (inst.opcode->iclass == ldst_pos /* Unsigned immediate. */
> + && (inst.opcode->op == OP_STR_POS
> + || inst.opcode->op == OP_STRF_POS)))
> + && inst.operands[1].addr.base_regno == AARCH64_SP_REGNUM
> + && strcmp ("str", inst.opcode->name) == 0)
> + {
> + /* STR (immediate) */
> + unsigned int rt = inst.operands[0].reg.regno;
> + int32_t imm = inst.operands[1].addr.offset.imm;
> + unsigned rn = inst.operands[1].addr.base_regno;
Mixed "unsigned int" vs "unsigned" style.
> + int is64
"bool".
> + = (aarch64_get_qualifier_esize (inst.operands[0].qualifier) == 8);
> + gdb_assert (inst.operands[0].type == AARCH64_OPND_Rt
> + || inst.operands[0].type == AARCH64_OPND_Ft);
> +
> + if (inst.operands[0].type == AARCH64_OPND_Ft)
> + {
> + /* Only bottom 64-bit of each V register (D register) need
> + to be preserved. */
> + gdb_assert (inst.operands[0].qualifier == AARCH64_OPND_QLF_S_D);
> + rt += AARCH64_X_REGISTER_COUNT;
> + }
> +
> + pv_area_store (stack, pv_add_constant (regs[rn], imm),
> + is64 ? 8 : 4, regs[rt]);
> + if (inst.operands[1].addr.writeback)
> + regs[rn] = pv_add_constant (regs[rn], imm);
> + }
> else if (inst.opcode->iclass == testbranch)
> {
> /* Stop analysis on branch. */
> @@ -546,6 +575,52 @@ aarch64_analyze_prologue_test (void)
> == -1);
> }
> }
> +
> + /* Test a prologue in which STR is used and frame pointer is not
> + used. */
Thanks for the new comments. This helps.
> + {
> + struct aarch64_prologue_cache cache;
> + cache.saved_regs = trad_frame_alloc_saved_regs (gdbarch);
> +
> + const uint32_t insns[] = {
"static const". Sorry, my fault.
Othewrise, code-style-wise LGTM. Thanks much for updating.
I've not payed attention to Aarch64-specifics, TBC. I just
assume you got those right. :-)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-12-01 13:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 14:12 [PATCH 1/2] Add unit test to aarch64 prologue analyzer Yao Qi
2016-11-29 14:12 ` [PATCH 2/2] [AArch64] Recognize STR instruction in prologue Yao Qi
2016-11-30 18:33 ` Pedro Alves
2016-11-29 14:58 ` [PATCH 1/2] Add unit test to aarch64 prologue analyzer Antoine Tremblay
2016-11-30 11:15 ` Yao Qi
2016-11-30 11:53 ` Antoine Tremblay
2016-11-30 16:35 ` Yao Qi
2016-11-30 16:42 ` Antoine Tremblay
2016-11-30 18:16 ` Pedro Alves
2016-11-30 18:29 ` Pedro Alves
2016-11-30 18:38 ` Pedro Alves
2016-11-30 19:30 ` Luis Machado
2016-12-01 12:53 ` Pedro Alves
2016-12-01 11:17 ` [PATCH 1/2 v2] " Yao Qi
2016-12-01 11:17 ` [PATCH 2/2 v2] [AArch64] Recognize STR instruction in prologue Yao Qi
2016-12-01 13:07 ` Pedro Alves [this message]
2016-12-02 9:42 ` Yao Qi
2016-12-01 12:57 ` [PATCH 1/2 v2] Add unit test to aarch64 prologue analyzer Pedro Alves
2016-12-01 15:21 ` Yao Qi
2016-12-01 16:04 ` Yao Qi
2016-12-01 18:05 ` Pedro Alves
2016-12-02 9:40 ` Yao Qi
2016-12-02 11:11 ` Pedro Alves
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=2b5ae431-5bfb-2adf-aafb-fa2cbda12619@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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