Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Ivo Raisr <ivo.raisr@oracle.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 20936 - provide sparc and sparcv9 target description XML files
Date: Wed, 25 Jan 2017 15:46:00 -0000	[thread overview]
Message-ID: <9351d864-e939-cc66-97e3-1c768bf78df1@redhat.com> (raw)
In-Reply-To: <e6065f2e-f76d-0190-dc34-d04da1a33e84@oracle.com>

(I know I'm quite behind this thread.)

On 01/06/2017 03:12 PM, Ivo Raisr wrote:
> 
> 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.

I don't quite understand this rationale, and I'm wondering if there's
a misunderstanding of register numbering somewhere (maybe mine!).

What exactly would go wrong if you just added the new registers
between the existing raw and pseudo registers?  Other ports do
that routinely.

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-01-25 15:46 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
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 [this message]
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=9351d864-e939-cc66-97e3-1c768bf78df1@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ivo.raisr@oracle.com \
    --cc=qiyaoltc@gmail.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