From: Peter Bergner <bergner@vnet.ibm.com>
To: Pedro Alves <palves@redhat.com>
Cc: binutils <binutils@sourceware.org>, Alan Modra <amodra@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
"Carl E. Love" <cel@us.ibm.com>,
gdb-patches@sourceware.org,
Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Subject: Re: [PATCH, committed] Finalize ISA 3.0 instruction support.
Date: Fri, 16 Sep 2016 20:50:00 -0000 [thread overview]
Message-ID: <f52ecd39-3788-b045-15c1-e4e4bb9689af@vnet.ibm.com> (raw)
In-Reply-To: <4abc6a00-868e-7d30-92c4-8fec407b76bf@redhat.com>
On 9/15/16 4:44 PM, Pedro Alves wrote:
> On 09/15/2016 10:18 PM, Peter Bergner wrote:
>> On 9/15/16 6:34 AM, Pedro Alves wrote:
>>> On 09/15/2016 04:26 AM, Peter Bergner wrote:
>>>> This patch modifies the ISA 3.0 instruction support to match the
>>>> finalized
>>>> ISA 3.0 documentation. Committed.
>>
>> Ok, I committed the following as obvious, which should clean up the
>> new GDB failures I caused. Sorry about the breakage!
>
> Thanks! I think it'd make sense to push these two patches to
> the gdb-7.12-branch branch (gdb 7.12 is not out yet, but it's close).
>
> Could you do that?
Ok, I committed the gas changes (first patch) to gdb-7.12-branch.
When I tried applying the follow up gdb testsuite trunk changes,
I noticed that the gdb-7.12-branch doesn't have any power9 tests,
so that patch doesn't make sense for the branch.
Peter
prev parent reply other threads:[~2016-09-16 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2033161b-a9eb-3ddc-bb98-db8ee1eed6a5@vnet.ibm.com>
[not found] ` <4899c29a-2401-a221-dccf-9b22325fe054@redhat.com>
2016-09-15 21:20 ` Peter Bergner
2016-09-15 21:44 ` Pedro Alves
2016-09-16 15:22 ` Peter Bergner
2016-09-16 21:50 ` Peter Bergner
2016-09-16 20:50 ` Peter Bergner [this message]
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=f52ecd39-3788-b045-15c1-e4e4bb9689af@vnet.ibm.com \
--to=bergner@vnet.ibm.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=cel@us.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=wschmidt@linux.vnet.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