From: Jim Blandy <jimb@red-bean.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] spelling errors in rs6000-tdep.c
Date: Thu, 22 Dec 2005 04:56:00 -0000 [thread overview]
Message-ID: <8f2776cb0512201135i727e1ce0q14f2728b57b9e015@mail.gmail.com> (raw)
In-Reply-To: <20051220180054.GY991@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
At the risk of bike-shedding...
The fact that "nonexistent" is in regular use doesn't mean that
"existent" is entirely kosher:
http://www.ling.upenn.edu/courses/ling001/mccord.html
In the 'sz' fields, I think "nonexistent" is right: it's zero when the
registers don't exist.
But in rs6000_gdbarch_init, "extant" is a much better word, having the
connotations of "already".
I've committed the attached.
[-- Attachment #2: jimb.gdb-rs6000-extant-doc-fix.patch --]
[-- Type: text/x-patch, Size: 986 bytes --]
gdb/ChangeLog:
2005-12-20 Jim Blandy <jimb@redhat.com>
* rs6000-tdep.c (rs6000_gdbarch_init): Doc fix.
Index: gdb/rs6000-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
retrieving revision 1.251
diff -c -p -r1.251 rs6000-tdep.c
*** gdb/rs6000-tdep.c 20 Dec 2005 17:57:44 -0000 1.251
--- gdb/rs6000-tdep.c 20 Dec 2005 19:32:44 -0000
*************** rs6000_gdbarch_init (struct gdbarch_info
*** 3120,3126 ****
wordsize = 4;
}
! /* Find a candidate among existent architectures. */
for (arches = gdbarch_list_lookup_by_info (arches, &info);
arches != NULL;
arches = gdbarch_list_lookup_by_info (arches->next, &info))
--- 3120,3126 ----
wordsize = 4;
}
! /* Find a candidate among extant architectures. */
for (arches = gdbarch_list_lookup_by_info (arches, &info);
arches != NULL;
arches = gdbarch_list_lookup_by_info (arches->next, &info))
prev parent reply other threads:[~2005-12-20 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 4:27 Joel Brobecker
2005-12-22 4:46 ` Joel Brobecker
2005-12-22 4:56 ` Jim Blandy [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=8f2776cb0512201135i727e1ce0q14f2728b57b9e015@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=brobecker@adacore.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