From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MIPS/Linux: Register number overlap in target descriptions
Date: Tue, 04 Dec 2007 15:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0712041512170.21152@perivale.mips.com> (raw)
In-Reply-To: <20071204151051.GA3966@caradoc.them.org>
On Tue, 4 Dec 2007, Daniel Jacobowitz wrote:
> No, those numberings are different. They are used for internal
> register layout, but only sent to the target if there is no XML
> description. So a mismatch is fine except when you're trying to
> retain compatibility with legacy stubs.
Ah, I see.
> Of course, I was trying. Not sure how I missed this - did it have
> any symptoms?
I just spotted it while putting support for DSP registers I am about to
submit in line with HEAD.
> Patch is OK. After this, I hope the register numbers line up with
> mips-elf again; I think they do.
It looks like.
Maciej
prev parent reply other threads:[~2007-12-04 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 15:01 Maciej W. Rozycki
2007-12-04 15:10 ` Daniel Jacobowitz
2007-12-04 15:20 ` Maciej W. Rozycki [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=Pine.LNX.4.61.0712041512170.21152@perivale.mips.com \
--to=macro@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
/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