[patch] h8300/*: Fix comment typos.

[Kazu Hirata]

Hi,

Attached is a patch to fix comment typos.  Committed as obvious.

Kazu Hirata

2002-01-10  Kazu Hirata  <kazu@hxi.com>

	* config/h8300/h8300.h: Fix comment typos.
	* config/h8300/h8300.md: Likewise.
	* config/h8300/lib1funcs.asm: Likewise.

Index: h8300.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/h8300/h8300.h,v
retrieving revision 1.66
diff -u -r1.66 h8300.h
--- h8300.h	2002/01/10 19:20:10	1.66
+++ h8300.h	2002/01/10 21:27:43
@@ -243,7 +243,7 @@
 #define PCC_BITFIELD_TYPE_MATTERS  0
 
 /* No data type wants to be aligned rounder than this.
-   32 bit values are aligned as such on the 300h for speed.  */
+   32 bit values are aligned as such on the H8/300H and H8/S for speed.  */
 #define BIGGEST_ALIGNMENT \
 (((TARGET_H8300H || TARGET_H8300S) && ! TARGET_ALIGN_300) ? 32 : 16)
 
Index: h8300.md
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/h8300/h8300.md,v
retrieving revision 1.50
diff -u -r1.50 h8300.md
--- h8300.md	2002/01/10 17:24:05	1.50
+++ h8300.md	2002/01/10 21:27:43
@@ -44,11 +44,12 @@
 ;; "worst case" and then be adjusted to their correct values by
 ;; h8300_adjust_insn_length.
 
-;; On the h8300h, adds/subs operate on the 32bit "er" registers.  Right
-;; now GCC doesn't expose the "e" half to the compiler, so using add/subs
-;; for addhi and subhi is safe.
-;; Long term, we want to expose the "e" half to the compiler (gives us
-;; 8 more 16bit registers).  At that point addhi and subhi can't use adds/subs.
+;; On the H8/300H and H8/S, adds/subs operate on the 32bit "er"
+;; registers.  Right now GCC doesn't expose the "e" half to the
+;; compiler, so using add/subs for addhi and subhi is safe.  Long
+;; term, we want to expose the "e" half to the compiler (gives us 8
+;; more 16bit registers).  At that point addhi and subhi can't use
+;; adds/subs.
 
 ;; There's currently no way to have a insv/extzv expander for the H8/300H
 ;; because word_mode is different for the H8/300 and H8/300H.
@@ -1600,7 +1601,7 @@
 
 ;; Call subroutine with no return value.
 
-;; ??? Even though we use HImode here, this works for the 300h.
+;; ??? Even though we use HImode here, this works on the H8/300H and H8/S.
 
 (define_insn "call"
   [(call (match_operand:QI 0 "call_insn_operand" "or")
@@ -1623,7 +1624,7 @@
 ;; Call subroutine, returning value in operand 0
 ;; (which must be a hard register).
 
-;; ??? Even though we use HImode here, this works on the 300h.
+;; ??? Even though we use HImode here, this works on the H8/300H and H8/S.
 
 (define_insn "call_value"
   [(set (match_operand 0 "" "=r")
Index: lib1funcs.asm
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/h8300/lib1funcs.asm,v
retrieving revision 1.9
diff -u -r1.9 lib1funcs.asm
--- lib1funcs.asm	2001/08/30 17:51:04	1.9
+++ lib1funcs.asm	2002/01/10 21:27:43
@@ -767,7 +767,7 @@
 #ifdef L_fixunssfsi_asm
 /* For the h8300 we use asm to save some bytes, to
    allow more programs to fit into the tiny address
-   space.  For h8300h / h8s, the C version is good enough.  */
+   space.  For the H8/300H and H8S, the C version is good enough.  */
 #ifdef __H8300__
 /* We still treat NANs different than libgcc2.c, but then, the
    behaviour is undefined anyways.  */