This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH] Bug 20936 - provide sparc and sparcv9 target description XML files
- From: Pedro Alves <palves at redhat dot com>
- To: Ivo Raisr <ivo dot raisr at oracle dot com>, Yao Qi <qiyaoltc at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 25 Jan 2017 15:46:24 +0000
- Subject: Re: [PATCH] Bug 20936 - provide sparc and sparcv9 target description XML files
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <20161206152616.GC28789@E107787-LIN> <firstname.lastname@example.org> <email@example.com> <20161212125331.GB25542@E107787-LIN> <firstname.lastname@example.org> <20170105143109.GA21293@E107787-LIN> <email@example.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 <firstname.lastname@example.org>
> 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