From: Daniel Jacobowitz <dan@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: hjl.tools@gmail.com, gdb-patches@sourceware.org
Subject: Re: PATCH: Add regcache_raw_supply_part/regcache_raw_collect_part
Date: Wed, 03 Feb 2010 14:00:00 -0000 [thread overview]
Message-ID: <20100203140011.GB27938@caradoc.them.org> (raw)
In-Reply-To: <201002030914.o139E4Ti027331@glazunov.sibelius.xs4all.nl>
On Wed, Feb 03, 2010 at 10:14:04AM +0100, Mark Kettenis wrote:
> I think introducing these functions would be a mistake. If you're not
> careful, you'll end up with a register cache where part of some
> registers is filled with garbage.
I agree.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2010-02-03 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 3:31 H.J. Lu
2010-02-03 9:14 ` Mark Kettenis
2010-02-03 13:46 ` H.J. Lu
2010-02-03 14:00 ` Daniel Jacobowitz [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=20100203140011.GB27938@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--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