From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com
Subject: Re: Language of registers
Date: Wed, 06 Dec 2006 22:55:00 -0000 [thread overview]
Message-ID: <17783.17097.37781.935178@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061206220333.GB14086@nevyn.them.org>
Daniel Jacobowitz writes:
> On Thu, Dec 07, 2006 at 10:49:57AM +1300, Nick Roberts wrote:
> > > When using variable objects, the frontend already has the
> > > parsing/display code.
> >
> > What would your variable object print for xmm1?
>
> Instead of a big string, it could have a triangle to expand xmm1,
> display it as uint32_t[4] and uint8_t[16] on different lines... just
> like we do for structures, right?
OK, I see now. I'm not familiar with these large registers (just the ones that
hold one value!). I was just thinking that maybe variable objects are `heavy
armour' for registers and that it might be simpler to change the output format
of the -data-list-* commands instead.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-12-06 22:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:54 Nick Roberts
2006-12-06 22:03 ` Daniel Jacobowitz
2006-12-06 22:55 ` Nick Roberts [this message]
2006-12-06 23:10 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2006-11-27 0:43 Nick Roberts
2006-11-27 6:32 ` Vladimir Prus
2006-11-27 7:37 ` Eli Zaretskii
2006-11-25 11:22 Vladimir Prus
2006-11-27 14:03 ` Daniel Jacobowitz
2006-11-28 17:12 ` Vladimir Prus
2006-11-28 17:23 ` Daniel Jacobowitz
2006-11-28 18:09 ` Vladimir Prus
2006-12-01 14:32 ` Daniel Jacobowitz
2006-12-01 18:03 ` Jim Ingham
2006-11-29 10:12 ` Vladimir Prus
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=17783.17097.37781.935178@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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