From: David Anderson <davea@quasar.engr.sgi.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] regcache.c spelling fix
Date: Wed, 12 May 2004 17:56:00 -0000 [thread overview]
Message-ID: <200405121744.i4CHipBo1545739@quasar.engr.sgi.com> (raw)
Comment spelling RFA, regcache.c
Paperwork is up to date, but currently ssh access not
working for me so if someone could check this in? If someone
folds it into another regcache.c patch no need to mention me at
all...
2004-05-12 David Anderson <davea@sgi.com>
* regcache.c (struct regcache_descr): fix comment spelling.
Index: gdb/regcache.c
===================================================================
RCS file: /cvs/src/src/gdb/regcache.c,v
retrieving revision 1.113
diff -p -r1.113 regcache.c
*** gdb/regcache.c 26 Apr 2004 09:49:36 -0000 1.113
--- gdb/regcache.c 12 May 2004 17:33:09 -0000
*************** struct regcache_descr
*** 64,72 ****
/* The cooked register space. Each cooked register in the range
[0..NR_RAW_REGISTERS) is direct-mapped onto the corresponding raw
register. The remaining [NR_RAW_REGISTERS
! .. NR_COOKED_REGISTERS) (a.k.a. pseudo regiters) are mapped onto
both raw registers and memory by the architecture methods
! gdbarch_register_read and gdbarch_register_write. */
int nr_cooked_registers;
long sizeof_cooked_registers;
long sizeof_cooked_register_valid_p;
--- 64,72 ----
/* The cooked register space. Each cooked register in the range
[0..NR_RAW_REGISTERS) is direct-mapped onto the corresponding raw
register. The remaining [NR_RAW_REGISTERS
! .. NR_COOKED_REGISTERS) (a.k.a. pseudo registers) are mapped onto
both raw registers and memory by the architecture methods
! gdbarch_pseudo_register_read and gdbarch_pseudo_register_write. */
int nr_cooked_registers;
long sizeof_cooked_registers;
long sizeof_cooked_register_valid_p;
Thanks.
David Anderson
next reply other threads:[~2004-05-12 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 17:56 David Anderson [this message]
2004-05-14 7:17 ` Jim Blandy
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=200405121744.i4CHipBo1545739@quasar.engr.sgi.com \
--to=davea@quasar.engr.sgi.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