From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] ppc: Add Power ISA 3.0/POWER9 instructions record support
Date: Wed, 21 Sep 2016 16:40:00 -0000 [thread overview]
Message-ID: <7c304888-44d5-e8c4-c973-a034a24ecec1@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160921161715.C2D7A10FDC1@oc8523832656.ibm.com>
On 09/21/2016 01:17 PM, Ulrich Weigand wrote:
> Edjunior Barbosa Machado wrote:
>
>> first, thanks for the review. I've talked to the kernel developers and
>> reworked the patch.
>
> This is looking good to me now!
>
>> gdb/ChangeLog:
>> 2016-09-21 Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
>>
>> * rs6000-tdep.c (PPC_DQ): New macro.
>> (ppc_process_record_op4): Add Power ISA 3.0 instructions.
>> (ppc_process_record_op19): Likewise.
>> (ppc_process_record_op31): Likewise.
>> (ppc_process_record_op59): Likewise.
>> (ppc_process_record_op60): Likewise.
>> (ppc_process_record_op63): Likewise.
>> (ppc_process_record): Likewise.
>> (ppc_process_record_op61): New function.
>
> This is OK.
>
Thanks for the quick reply, Uli! The patch was just pushed to master:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=6ec2b213de6962ceeb81bfa33354ea6e60c57049
--
Edjunior
next prev parent reply other threads:[~2016-09-21 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 16:04 Edjunior Barbosa Machado
2016-09-21 16:23 ` Ulrich Weigand
2016-09-21 16:40 ` Edjunior Barbosa Machado [this message]
2016-09-22 14:30 ` [PATCH] Fix build breakage from commit 6ec2b2 Edjunior Barbosa Machado
2016-09-22 14:32 ` Ulrich Weigand
2016-09-22 15:05 ` Edjunior Barbosa Machado
-- strict thread matches above, loose matches on Subject: below --
2016-09-20 15:33 [PATCH] ppc: Add Power ISA 3.0/POWER9 instructions record support Ulrich Weigand
2016-09-15 15:43 Edjunior Barbosa Machado
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=7c304888-44d5-e8c4-c973-a034a24ecec1@linux.vnet.ibm.com \
--to=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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