From: Andrew Cagney <ac131313@ges.redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Remove some write_register_bytes occurences from i386-tdep.c
Date: Sun, 18 Aug 2002 13:08:00 -0000 [thread overview]
Message-ID: <3D5FFEA6.9000306@ges.redhat.com> (raw)
In-Reply-To: <3D5FDD69.7000102@ges.redhat.com>
> As for write_register_bytes() can it be avoided? I've just posted ``regcache_cooked_write_with_offset_hack(). But I don't think that hack is right here. Perhaphs a single register read - modify - write function is needed?
Hmm,
I just hit a need for the same operation while implementing some pseudo
registers. Just adding:
regcache_raw_read_part(regcache,regnum,offset,length,buf)
regcache_raw_write_part(regcache,regnum,offset,length,buf)
Andrew
next prev parent reply other threads:[~2002-08-18 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-18 10:18 Mark Kettenis
2002-08-18 10:46 ` Andrew Cagney
2002-08-18 13:08 ` Andrew Cagney [this message]
2002-08-18 13:19 ` Mark Kettenis
2002-08-18 13:35 ` [PATCH] regcache raw read/write partial; Was: " Andrew Cagney
2002-08-18 17:38 ` Andrew Cagney
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=3D5FFEA6.9000306@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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