This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] h8300 "info registers" fix
On Fri, Sep 22, 2006 at 08:21:12PM -0700, Jim Blandy wrote:
>
> Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> > Not weird at all; it's the same convention we use for storing values.
> >
> > Bet most debug interfaces you've seen lately actually use
> > little-endian byte order.
They're frequently organized in integer multiples of the word size,
which are documented to return in host uint32_t's. If the underlying
"register" is really bigger than that, then the stub is responsible
for composing.
> No, they're actually documented to return them in host byte order.
> You read a register, you get an integer.
>
> (Well, Daniel's seen more than me, but this is so of the ones I have
> seen.)
Yep. I can think offhand of four different JTAG-related debug
interfaces I've worked with in the last six months, all of which did
this. Then, we transform the number from host endianness (on
the machine running the stub) to target endianness (the device)
before passing it over TCP/IP to GDB. All a bit messy, but you lose
some no matter which order you pick :-)
--
Daniel Jacobowitz
CodeSourcery