From: Ivo Raisr <ivo.raisr@oracle.com>
To: GDB <gdb-patches@sourceware.org>
Cc: Pedro Alves <pedro@palves.net>, Jiong Wang <jiong.wang@foss.arm.com>
Subject: Re: [Patch] New gdbarch method "dwarf_cfa_op" and migrate SPARC to it
Date: Fri, 21 Apr 2017 19:53:00 -0000 [thread overview]
Message-ID: <1e9bab7b-affc-8724-4143-ddd0c7a6f6f0@oracle.com> (raw)
In-Reply-To: <c92da4cc-a713-6055-f521-6164f5a6e6d8@palves.net>
On 21.4.2017 21:37, Pedro Alves wrote:
> On 04/21/2017 03:56 PM, Jiong Wang wrote:
>
>> Hi Ivo,
>>
>> Thanks very much for testing this on SPARC platform.
>>
>> What's really reused is the DWARF CFA number 0x2d behind
>> DW_CFA_GNU_window_save. It is in vendor extension space (
>> DW_CFA_lo_user.. DW_CFA_hi_user) so the semantics depends on vendor
>> interpreation.
>
> Maybe the commit log could/should be simplified, because
> I was confused too.
>
> Doesn't the Aarch64 version of the opcode have its own
> name, like DW_CFA_GNU_Aarch64_whatever, even if it reuses the
> opcode number? I think that would help a lot going forward
> if it had one. E.g., it'd avoid confusion, allow for easier
> searching, etc.
Introducing Aarch64 specific name would be very much appreciated.
+1 here!
I.
next prev parent reply other threads:[~2017-04-21 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 10:17 Jiong Wang
2017-04-21 20:45 ` Ivo Raisr
2017-04-21 18:33 ` Jiong Wang
2017-04-21 19:37 ` Pedro Alves
2017-04-21 19:53 ` Ivo Raisr [this message]
2017-04-25 10:40 ` Jiong Wang
2017-04-26 8:49 ` Ivo Raisr
2017-04-26 9:22 ` 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=1e9bab7b-affc-8724-4143-ddd0c7a6f6f0@oracle.com \
--to=ivo.raisr@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=jiong.wang@foss.arm.com \
--cc=pedro@palves.net \
/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