From: Jiong Wang <jiong.wang@foss.arm.com>
To: Cary Coutant <ccoutant@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Mark Wielaard <mjw@redhat.com>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
GDB <gdb-patches@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: [1/9][RFC][DWARF] Reserve three DW_OP numbers in vendor extension space
Date: Tue, 03 Jan 2017 09:32:00 -0000 [thread overview]
Message-ID: <451acea7-a17f-32a0-9f25-fefe73e952d3@foss.arm.com> (raw)
In-Reply-To: <CAJimCsEnnDKC9vGE5XZWqzjmsF4C2Z7FOfxcF8Y3L2in=MMk_w@mail.gmail.com>
On 28/12/16 19:54, Cary Coutant wrote:
>> OK on this proposal and to install this patch to gcc trunk?
>>
>> Hi GDB, Binutils maintainer:
>>
>> OK on this proposal and install this patch to binutils-gdb master?
>>
>> include/
>> 2016-11-29 Richard Earnshaw <rearnsha@arm.com>
>> Jiong Wang <jiong.wang@arm.com>
>>
>> * dwarf2.def (DW_OP_AARCH64_operation): Reserve the number 0xea.
> This is OK, but:
>
> +/* AARCH64 extensions.
> + DW_OP_AARCH64_operation takes one mandatory unsigned LEB128 operand.
> + Bits[6:0] of this operand is the action code, all others bits are
> initialized
> + to 0 except explicitly documented for one action. Please refer
> AArch64 DWARF
> + ABI documentation for details. */
>
> Is it possible to include a stable URL that points to the ABI document?
Hi Cary,
Thanks for the review.
Currently there is no URL for this AArch64 DWARF ABI updates. I will
update the comments as soon as the stable URL is available.
Regards,
Jiong
next prev parent reply other threads:[~2017-01-03 9:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c9da17a6-c3de-4466-c023-4e4ddbe38efb@foss.arm.com>
2016-11-11 18:22 ` Jiong Wang
2016-11-11 19:39 ` Jakub Jelinek
2016-11-15 16:00 ` Jiong Wang
2016-11-15 16:18 ` Jakub Jelinek
2016-11-15 16:48 ` Jiong Wang
2016-11-15 19:25 ` Richard Earnshaw (lists)
2016-11-16 10:00 ` Jiong Wang
[not found] ` <1479304496.14569.256.camel@redhat.com>
2016-11-16 14:02 ` Jakub Jelinek
2016-11-30 11:15 ` Jiong Wang
2016-11-30 18:25 ` Yao Qi
2016-12-12 13:40 ` [Ping~][1/9][RFC][DWARF] " Jiong Wang
2016-12-19 13:59 ` [Ping^2][1/9][RFC][DWARF] " Jiong Wang
2016-12-28 18:21 ` [Ping^3][1/9][RFC][DWARF] " Jiong Wang
2016-12-28 19:54 ` [1/9][RFC][DWARF] " Cary Coutant
2017-01-03 9:32 ` Jiong Wang [this message]
2017-01-03 10:10 ` Jiong Wang
2017-01-03 10:57 ` Yao Qi
2017-01-03 15:21 ` Nick Clifton
2017-01-03 17:47 ` Yao Qi
2016-11-30 21:44 ` Cary Coutant
2016-12-01 10:42 ` Richard Earnshaw (lists)
2016-12-01 11:09 ` Jiong Wang
2016-11-15 16:51 ` Jiong Wang
2016-12-28 19:48 ` Cary Coutant
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=451acea7-a17f-32a0-9f25-fefe73e952d3@foss.arm.com \
--to=jiong.wang@foss.arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
--cc=mjw@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