From: Jiong Wang <jiong.wang@foss.arm.com>
To: Pedro Alves <palves@redhat.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: [AArch64][3/6] DWARF unwinder support for signed return address
Date: Thu, 10 Aug 2017 13:35:00 -0000 [thread overview]
Message-ID: <d039e0c0-1b27-d600-4e72-4fb8cd4911c3@foss.arm.com> (raw)
In-Reply-To: <ea6f2662-841b-0ce4-51f5-455b221c342f@redhat.com>
On 10/08/17 12:08, Pedro Alves wrote:
> On 08/09/2017 01:17 PM, Jiong Wang wrote:
>> +
>> + /* Only DW_CFA_GNU_window_save is expected on AArch64. */
>> + if (op != DW_CFA_GNU_window_save)
>> + return false;
>> +
> Was there any progress in giving this an Aarch64-specific name
> to avoid confusion? FYI, I was confused by this again for a couple
> minutes when I read it, until I remembered the previous discussions.
Hi Pedro,
Yes, We can add DW_CFA_AARCH64_negate_ra_state to dwarf2.def, with the same
number of DW_CFA_GNU_window_save, then need to introduce a new DW_CFA_DUP
to avoid duplicated case value trouble when auto-generate switch/case for
returning CFA name. Will post patch to GCC then can be synced to binutils-gdb
onced approved.
>
>> +/* Implement the execute_dwarf_cfa_vendor_op method. */
>> +
>> +static bool
>> +aarch64_execute_dwarf_cfa_vendor_op (struct gdbarch *gdbarch, gdb_byte op,
>> + struct dwarf2_frame_state *fs)
>> +{
>> + struct dwarf2_frame_state_reg *ra_state_column;
>> + static unsigned char exp_0 = 0x30; /* DW_OP_lit0. */
>> + static unsigned char exp_1 = 0x31; /* DW_OP_lit1. */
> Can these be static const? (likewise elsewhere in the patch.)
>
> Also, gdb_byte.
Will fix in the next update.
Thanks.
Regards,
Jiong
next prev parent reply other threads:[~2017-08-10 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c8484136-c4f2-cda2-6a0d-f8293b111cdd@foss.arm.com>
2017-08-09 12:17 ` Jiong Wang
2017-08-10 11:08 ` Pedro Alves
2017-08-10 13:35 ` Jiong Wang [this message]
2017-08-09 12:18 ` [AArch64][4/6] Prologue scan " Jiong Wang
2017-08-09 12:18 ` [AArch64][5/6] Implement gdbarch_core_read_description Jiong Wang
2017-08-09 14:22 ` Yao Qi
2017-08-09 14:57 ` Jiong Wang
2017-08-09 15:43 ` Jiong Wang
2017-08-09 16:04 ` Yao Qi
2017-08-09 16:40 ` Jiong Wang
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=d039e0c0-1b27-d600-4e72-4fb8cd4911c3@foss.arm.com \
--to=jiong.wang@foss.arm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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