Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@specifix.com>
To: gdb-patches@sourceware.org
Cc: fnf@specifix.com
Subject: [patch] Spelling fixes
Date: Sat, 20 May 2006 00:27:00 -0000	[thread overview]
Message-ID: <200605191646.22730.fnf@specifix.com> (raw)

Checked in under the 'obvious fix rule', though not sure if current
practice is to record in ChangeLog or not.

2006-05-19  Fred Fish  <fnf@specifix.com>

	* Makefile.in: Fix spelling of 'explicitly' and 'explicit'.
	* dwarfread.c: Fix spelling of 'unexpected'.
	* mips-tdep.c: Fix spelling of 'possible' and 'Determine'.
	* stack.c: Fix spelling of 'RETURN_VALUE'.
	

Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.818
diff -u -p -r1.818 Makefile.in
--- Makefile.in	17 May 2006 14:53:02 -0000	1.818
+++ Makefile.in	19 May 2006 20:41:29 -0000
@@ -1274,7 +1274,7 @@ clean-tui:
 # describe removing files; the only sort of "re-create a distribution"
 # functionality described is if the distributed files are unmodified.
 # NB: While GDBSERVER might be configured on native systems, it isn't
-# always included in SUBDIRS.  Remove the gdbserver files explictly.
+# always included in SUBDIRS.  Remove the gdbserver files explicitly.
 distclean: clean
 	@$(MAKE) $(FLAGS_TO_PASS) DO=distclean "DODIRS=$(SUBDIRS)" subdir_do
 	rm -f gdbserver/config.status gdbserver/config.log
@@ -1489,7 +1489,7 @@ ALLDEPFILES = \
 	xcoffread.c xcoffsolib.c \
 	xstormy16-tdep.c
 
-# Some files need explict build rules (due to -Werror problems) or due
+# Some files need explicit build rules (due to -Werror problems) or due
 # to sub-directory fun 'n' games.
 
 # Provide explicit rule/dependency - works for more makes.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.196
diff -u -p -r1.196 dwarf2read.c
--- dwarf2read.c	13 May 2006 15:46:38 -0000	1.196
+++ dwarf2read.c	19 May 2006 20:41:32 -0000
@@ -7346,7 +7346,7 @@ read_type_die (struct die_info *die, str
       read_base_type (die, cu);
       break;
     default:
-      complaint (&symfile_complaints, _("unexepected tag in read_type_die: '%s'"),
+      complaint (&symfile_complaints, _("unexpected tag in read_type_die: '%s'"),
 		 dwarf_tag_name (die->tag));
       break;
     }
Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.391
diff -u -p -r1.391 mips-tdep.c
--- mips-tdep.c	5 May 2006 18:04:04 -0000	1.391
+++ mips-tdep.c	19 May 2006 20:41:34 -0000
@@ -2323,7 +2323,7 @@ struct mips_objfile_private
 
 /* According to the current ABI, should the type be passed in a
    floating-point register (assuming that there is space)?  When there
-   is no FPU, FP are not even considered as possibile candidates for
+   is no FPU, FP are not even considered as possible candidates for
    FP registers and, consequently this returns false - forces FP
    arguments into integer registers. */
 
@@ -2644,7 +2644,7 @@ mips_eabi_push_dummy_call (struct gdbarc
   return sp;
 }
 
-/* Determin the return value convention being used.  */
+/* Determine the return value convention being used.  */
 
 static enum return_value_convention
 mips_eabi_return_value (struct gdbarch *gdbarch,
Index: stack.c
===================================================================
RCS file: /cvs/src/src/gdb/stack.c,v
retrieving revision 1.138
diff -u -p -r1.138 stack.c
--- stack.c	30 Mar 2006 16:37:13 -0000	1.138
+++ stack.c	19 May 2006 20:41:34 -0000
@@ -1829,7 +1829,7 @@ If you continue, the return value that y
      frame).  */
   frame_pop (get_current_frame ());
 
-  /* Store RETURN_VAUE in the just-returned register set.  */
+  /* Store RETURN_VALUE in the just-returned register set.  */
   if (return_value != NULL)
     {
       struct type *return_type = value_type (return_value);


             reply	other threads:[~2006-05-19 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20  0:27 Fred Fish [this message]
2006-05-23  0:21 ` 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=200605191646.22730.fnf@specifix.com \
    --to=fnf@specifix.com \
    --cc=gdb-patches@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