From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: frysk-core/frysk proc/BankRegister.java proc/C ...
Date: Wed, 10 Oct 2007 13:49:00 -0000 [thread overview]
Message-ID: <470CD854.9090308@redhat.com> (raw)
In-Reply-To: <470CD4FD.90202@redhat.com>
Andrew Cagney wrote:
> I'm not sure what you mean, the offset/length are for within the
> specified register, and start is an offset into the byte buffer. Two
> things change: tThe code that implements register accesses isn't being
> moved to the task; but the way to access registers is now simpler,
> contrast:
> Task.getRegister(IA32Register.XIP)
> with:
> Task.getIsa().getBankRegister("xip").getRegister(task)
> the internals, though cleaned up will still be very similar.
>
Ok that makes much more sense. Thanks. The other api threw me, but if
this is the eventual user facing api, that will be great.
Regards
Phil
prev parent reply other threads:[~2007-10-10 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071009194630.3523.qmail@sourceware.org>
2007-10-09 20:05 ` Phil Muldoon
2007-10-10 3:51 ` Andrew Cagney
2007-10-10 6:49 ` Phil Muldoon
2007-10-10 13:36 ` Andrew Cagney
2007-10-10 13:49 ` Phil Muldoon [this message]
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=470CD854.9090308@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).