From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Basic structure to describe register formats
Date: Fri, 01 Feb 2002 15:28:00 -0000 [thread overview]
Message-ID: <3C5B248B.8070201@cygnus.com> (raw)
In-Reply-To: <20020201170917.A21225@nevyn.them.org>
> You mean - 32:r1?
>>
>> I think the ``4'' indicates 4*2 hex digits. Digit pairs ordered either
>> big or little endian. Yes it could be bits, however, the value would
>> always need to be divisible by 8.
>
>
> No, I don't think it needs to be divisible by 8. If it did I wouldn't
> feel the need to represent the 8.
>
> For instance:
> - ia64 has 1-bit registers that we currently transmit as either bytes
> or words, IIRC.
Here, I don't think we're worried about how many bits a register
occupies. Rather, how that register is is represented when ``spilt''
into memory (to use the way the ia64 describes its in memory FP register
format). It is that ``spilt'' format, transmitted as ascii encoded hex
digit pairs, that is being described.
A target with registers one bit in size could either spill each register
into individual byte/word/... or combine them into a single word. For
the latter, I think we'd end up with something like ``8:f0f1f2f3f4f5'',
> - someone mentioned recently working on a non-8-bit target for GDB,
> but he wasn't quite ready to contribute it.
Yes.
> But it will be divisible by 8 for now, so we'll just ignore that for
> the moment.
:-)
Andrew
next prev parent reply other threads:[~2002-02-01 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 12:22 Daniel Jacobowitz
2002-02-01 13:10 ` Andrew Cagney
2002-02-01 13:21 ` Daniel Jacobowitz
2002-02-01 13:50 ` Andrew Cagney
2002-02-01 14:09 ` Daniel Jacobowitz
2002-02-01 15:28 ` Andrew Cagney [this message]
2002-02-01 14:01 ` Frank Ch. Eigler
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=3C5B248B.8070201@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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