This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [remote] Make registers network byteordered?
- To: Jim Blandy <jimb at cygnus dot com>
- Subject: Re: [remote] Make registers network byteordered?
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 06 Dec 2000 11:14:43 +1100
- Cc: GDB Discussion <gdb at sourceware dot cygnus dot com>
- References: <3A2C4305.6D9E53B3@cygnus.com> <np1yvm8plo.fsf@zwingli.cygnus.com>
Jim Blandy wrote:
>
> Andrew Cagney <ac131313@cygnus.com> writes:
>
> >
> > Hello,
> >
> > At present the target sends back registers in target byte order format
> > vis:
> >
> > T0525:c4060280ffffffff;1d:c0ffff81ffffffff;
> >
> > I'd like to think about a tweek to this part of the protocol so that the
> > format:
> >
> > T0525=ffffffff80020664;1d=ffffffff81ffffc0;
> >
> > is accepted. The thing I can't figure out is now to also change the
> > [pP] packets so that GDB can correctly detect targets that support this
> > format when writing registers.
> >
> > General comments?
>
> What's the point? Simply that registers don't have an endianness?
Several motivations:
o there is no robust way of
communicating a change in
endianess through the protocol.
This should be trivial. Fetch
the status register and check
the endian bit. Nope.
o I've had it with trying to read
what are endian independant values
backwards.
enjoy,
Andrew