Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Ivo Raisr <ivo.raisr@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 20936 - provide sparc and sparcv9 target description XML files
Date: Mon, 09 Jan 2017 17:35:00 -0000	[thread overview]
Message-ID: <20170109173515.GC9518@E107787-LIN> (raw)
In-Reply-To: <e6065f2e-f76d-0190-dc34-d04da1a33e84@oracle.com>

On 17-01-06 16:12:09, Ivo Raisr wrote:
> 
> I think I see the line now as well. Please find patch #1 together
> with a ChangeLog entry.
> The patch was successfully built and tested on Solaris sparc.
> After you find it ok, I will prepare patch #2.
> I.

> ChangeLog entry:
> 2017-01-06  Ivo Raisr  <ivo.raisr@oracle.com>
> 
> 	Split real and pseudo registers in preparation for registers provided
> 	by a target. Registers provided by target description can have more real
> 	registers and pseudo registers need to be positioned after them.

We don't document "changes" in this way.  If you think it is important
to mention them, put them in the commit log.

> @@ -57,6 +63,12 @@ struct gdbarch_tdep
>    int pc_regnum;
>    int npc_regnum;
>  
> +  /* Register names specific for architecture (sparc32 vs. sparc64) */
> +  const char **fpu_register_names;
> +  size_t fpu_registers_num;
> +  const char **cp0_register_names;
> +  size_t cp0_registers_num;
> +

These four fields are added, but not used at all, so could you move
them to patch #2?

-- 
Yao (齐尧)


  reply	other threads:[~2017-01-09 17:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 11:41 Ivo Raisr
2016-12-06 15:26 ` Yao Qi
2016-12-06 23:46   ` Ivo Raisr
2016-12-06 23:58     ` Ivo Raisr
2016-12-12 12:54       ` Yao Qi
2017-01-04 17:43         ` Ivo Raisr
2017-01-05 14:31           ` Yao Qi
2017-01-06 15:12             ` Ivo Raisr
2017-01-09 17:35               ` Yao Qi [this message]
2017-01-09 21:18                 ` Ivo Raisr
2017-01-10  9:29                   ` Yao Qi
2017-01-11 13:15                     ` Ivo Raisr
2017-01-11 15:46                       ` Yao Qi
2017-01-12 11:09                         ` Ivo Raisr
2017-01-16 16:50                           ` Jose E. Marchesi
2017-01-25 15:46               ` Pedro Alves
2017-01-25 16:05                 ` Ivo Raisr
2017-01-25 16:24                   ` Pedro Alves
2017-01-25 16:26                     ` Ivo Raisr
2017-01-25 16:44                       ` Yao Qi
2017-01-17 21:38         ` Ivo Raisr
2017-01-25  5:46           ` Ivo Raisr
2017-01-25 22:42           ` Yao Qi
2017-01-26 11:23             ` Ivo Raisr
2016-12-11 17:23     ` Ivo Raisr

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=20170109173515.GC9518@E107787-LIN \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ivo.raisr@oracle.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