From: Jim Blandy <jimb@red-bean.com>
To: gdb-patches@sources.redhat.com
Subject: Fwd: RFA: GDB manual: clarify lack of restrictions on 'm' packets
Date: Wed, 16 Nov 2005 07:21:00 -0000 [thread overview]
Message-ID: <8f2776cb0511152238k6b99cd93w4787781ba1120119@mail.gmail.com> (raw)
In-Reply-To: <8f2776cb0511152223q4c1414f1l2218bc10dbdfa74e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Accidentally dropped gdb-patches from the recipients.
---------- Forwarded message ----------
From: Jim Blandy <jimb@red-bean.com>
Date: Nov 15, 2005 10:23 PM
Subject: Re: RFA: GDB manual: clarify lack of restrictions on 'm' packets
To: Eli Zaretskii <eliz@gnu.org>
On 11/15/05, Eli Zaretskii <eliz@gnu.org> wrote:
> > Some possibilities:
> >
> > @cindex alignment of remote memory accesses
> > @cindex size of remote memory accesses
> > @cindex memory, alignment and size of remote accesses
> > @cindex memory-mapped input/output and remote protocol
> > @cindex input/output, memory-mapped and remote protocol
> >
> > I could go on like that, but it feel like overkill. What do you think?
>
> #1 and #3 will do, I think.
For memory-mapped I/O, both alignment and size matter; I don't think
there's a sense in which one is more relevant to the question than the
other. So I've committed 1-3; patch attached. I'm happy to change it
if you disagree, of course.
2005-11-15 Jim Blandy <jimb@redhat.com>
* gdb.texinfo (Packets): Add index entries for 'm' packet
disclaimers.
[-- Attachment #2: jimb.gdb-doc-remote-protocol-index-m-disclaimer.patch --]
[-- Type: text/x-patch, Size: 903 bytes --]
gdb/doc/ChangeLog:
2005-11-15 Jim Blandy <jimb@redhat.com>
* gdb.texinfo (Packets): Add index entries for 'm' packet
disclaimers.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.290
diff -c -p -r1.290 gdb.texinfo
*** gdb/doc/gdb.texinfo 15 Nov 2005 19:58:30 -0000 1.290
--- gdb/doc/gdb.texinfo 16 Nov 2005 06:17:08 -0000
*************** data from memory for the response; even
*** 22332,22337 ****
--- 22332,22340 ----
and @var{length} is a multiple of the word size, the stub is free to
use byte accesses, or not. For this reason, this packet may not be
suitable for accessing memory-mapped I/O devices.
+ @cindex alignment of remote memory accesses
+ @cindex size of remote memory accesses
+ @cindex memory, alignment and size of remote accesses
Reply:
@table @samp
next prev parent reply other threads:[~2005-11-16 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 17:27 Jim Blandy
2005-11-16 4:47 ` Eli Zaretskii
[not found] ` <8f2776cb0511151158n20cc5636kc974bc0cf9d967c1@mail.gmail.com>
[not found] ` <uy83p6sf9.fsf@gnu.org>
[not found] ` <8f2776cb0511152223q4c1414f1l2218bc10dbdfa74e@mail.gmail.com>
2005-11-16 7:21 ` Jim Blandy [this message]
2005-11-16 9:14 ` Fwd: " Eli Zaretskii
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=8f2776cb0511152238k6b99cd93w4787781ba1120119@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb-patches@sources.redhat.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