From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: [patch] Breakpoint - only reset instruction bytes covered by breakpoint instruction bytes
Date: Tue, 10 Jul 2007 09:10:00 -0000 [thread overview]
Message-ID: <1184058613.3607.10.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46923B73.4050000@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
On Mon, 2007-07-09 at 09:43 -0400, Andrew Cagney wrote:
> Please use the ByteBuffer's bulk get/put methods.
Nice idea! But there is no bulk put method in ByteBuffer (there is a
bulk get(), but there are no single byte get() loops in the current
code). It would be nice to have a bulk put() method to optimize things,
so I filed bug http://sourceware.org/bugzilla/show_bug.cgi?id=4760
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-10 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 8:18 Mark Wielaard
2007-07-09 13:43 ` Andrew Cagney
2007-07-10 9:10 ` Mark Wielaard [this message]
2007-07-10 15:46 ` Andrew Cagney
2007-07-10 16:33 ` Chris Moller
2007-07-10 17:03 ` 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=1184058613.3607.10.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--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).