From: Jim Blandy <jimb@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, Michael.Snyder@palmsource.com,
gdb-patches@sourceware.org
Subject: Re: [RFC] h8300 "info registers" fix
Date: Sat, 23 Sep 2006 03:20:00 -0000 [thread overview]
Message-ID: <m364ffz2s7.fsf@codesourcery.com> (raw)
In-Reply-To: <200609230105.k8N15Hf7015324@elgar.sibelius.xs4all.nl> (Mark Kettenis's message of "Sat, 23 Sep 2006 03:05:17 +0200 (CEST)")
Mark Kettenis <mark.kettenis@xs4all.nl> writes:
>> Date: Wed, 13 Sep 2006 16:30:43 -0400
>> From: Daniel Jacobowitz <drow@false.org>
>>
>> On Wed, Sep 13, 2006 at 01:20:09PM -0700, Michael Snyder wrote:
>> > Grumble -- is the regcache kept in host order, or target order?
>>
>> Target order.
>>
>> [Which is apparently a bit weird; most debug interfaces I've seen
>> lately use host order.]
>
> 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.
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.)
next prev parent reply other threads:[~2006-09-23 3:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 15:05 Yoshinori Sato
2006-09-12 20:28 ` Michael Snyder
2006-09-13 2:28 ` Yoshinori Sato
2006-09-13 15:54 ` Yoshinori Sato
2006-09-13 20:05 ` Michael Snyder
2006-09-13 20:09 ` Daniel Jacobowitz
2006-09-13 20:23 ` Michael Snyder
2006-09-13 20:30 ` Daniel Jacobowitz
2006-09-13 20:59 ` Michael Snyder
2006-09-23 1:08 ` Mark Kettenis
2006-09-23 1:06 ` Mark Kettenis
2006-09-23 3:20 ` Jim Blandy [this message]
2006-09-23 3:26 ` Daniel Jacobowitz
2006-09-14 9:40 ` Yoshinori Sato
2006-09-19 16:28 ` Yoshinori Sato
2006-09-23 18:00 ` Mark Kettenis
2006-11-16 8:30 ` Yoshinori Sato
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=m364ffz2s7.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=Michael.Snyder@palmsource.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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