Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ivo Raisr <ivo.raisr@oracle.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 20928 - Decode %ccr into individual flags in sparcv9 register output
Date: Sun, 11 Dec 2016 17:22:00 -0000	[thread overview]
Message-ID: <a9f5fb47-54d1-2045-1ae6-1a97ff664471@oracle.com> (raw)
In-Reply-To: <4c1b29e0-8040-b9c8-5c45-5a5dd6acd835@oracle.com>

Any news here?
Thanks,
I.

On 6.12.2016 09:26, Ivo Raisr wrote:
>
>
> On 6.12.2016 03:03, Luis Machado wrote:
>> On 12/05/2016 05:45 PM, Ivo Raisr wrote:
>>>
>>>
>>> ChangeLog entry:
>>> 2016-12-05  Ivo Raisr  <ivo.raisr@oracle.com>
>>>
>>>     PR tdep/20928
>>>     Decode %ccr into individual flags in sparcv9 register output.
>>>     * sparc-tdep.h: Declare %ccr type.
>>>     * sparc64-tdep.c: Decode %ccr. Fix %fsr decoding.
>>
>> You need to mention the new sparc64_ccr_type field and the new 
>> function in the ChangeLog. Also, you need to add the function where 
>> you fixed the fsr decoding.
>
> Here is the fixed ChangeLog entry (and attached new version of patch):
>
> 2016-12-05  Ivo Raisr  <ivo.raisr@oracle.com>
>
>     PR tdep/20928
>     Decode %ccr into individual flags in sparcv9 register output.
>     * sparc-tdep.h: Declare sparc64_ccr_type.
>     * sparc64-tdep.c: Decode %ccr in a new function sparc64_ccr_type().
>     Fix %fsr decoding in sparc64_fsr_type().
>
>


  reply	other threads:[~2016-12-11 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 23:46 Ivo Raisr
2016-12-06  3:04 ` Luis Machado
2016-12-06  8:26   ` Ivo Raisr
2016-12-11 17:22     ` Ivo Raisr [this message]
2016-12-20  6:35     ` Ivo Raisr
2016-12-23 16:06       ` Luis 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=a9f5fb47-54d1-2045-1ae6-1a97ff664471@oracle.com \
    --to=ivo.raisr@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.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