summaryrefslogtreecommitdiff
path: root/gcc/config/m32r
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2003-07-03 12:34:09 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2003-07-03 12:34:09 +0000
commitdfd1079d966b07c4eaf22202750c75049cccd06b (patch)
tree1cd930fd71049c140cd57c9136427f478a715d30 /gcc/config/m32r
parent241af3ccf079a7b3ab71f3f0c1f8be5b81861693 (diff)
downloadgcc-dfd1079d966b07c4eaf22202750c75049cccd06b.tar.gz
* config/m32r/m32r.c: Fix comment typos.
* config/m68hc11/m68hc11.c: Likewise. * config/m68hc11/m68hc11.h: Likewise. * config/m68k/m68k.c: Likewise. * config/mcore/mcore.c: Likewise. * config/mcore/mcore.h: Likewise. * config/mcore/mcore.md: Likewise. * config/mips/mips.c: Likewise. * config/mips/mips.h: Likewise. * config/mips/mips.md: Likewise. * config/mips/netbsd.h: Likewise. * config/mn10300/mn10300.c: Likewise. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@68876 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/config/m32r')
-rw-r--r--gcc/config/m32r/m32r.c14
1 files changed, 7 insertions, 7 deletions
diff --git a/gcc/config/m32r/m32r.c b/gcc/config/m32r/m32r.c
index 3622d0657ea..e1dbce4bcad 100644
--- a/gcc/config/m32r/m32r.c
+++ b/gcc/config/m32r/m32r.c
@@ -1028,7 +1028,7 @@ m32r_pass_by_reference (type)
/* X and Y are two things to compare using CODE. Emit the compare insn and
return the rtx for compare [arg0 of the if_then_else].
If need_compare is true then the comparison insn must be generated, rather
- than being susummed into the following branch instruction. */
+ than being subsumed into the following branch instruction. */
rtx
gen_compare (code, x, y, need_compare)
@@ -1307,7 +1307,7 @@ gen_split_move_double (operands)
ld r1,r3+; ld r2,r3
if r3 were not used subsequently. However, the REG_NOTES aren't
- propigated correctly by the reload phase, and it can cause bad
+ propagated correctly by the reload phase, and it can cause bad
code to be generated. We could still try:
ld r1,r3+; ld r2,r3; addi r3,-4
@@ -1334,7 +1334,7 @@ gen_split_move_double (operands)
st r1,r3; st r2,+r3
if r3 were not used subsequently. However, the REG_NOTES aren't
- propigated correctly by the reload phase, and it can cause bad
+ propagated correctly by the reload phase, and it can cause bad
code to be generated. We could still try:
st r1,r3; st r2,+r3; addi r3,-4
@@ -1579,7 +1579,7 @@ m32r_sched_reorder (stream, verbose, ready, n_readyp, clock)
rtx * new_tail = new_head + (n_ready - 1);
int i;
- /* Loop through the instructions, classifing them as short/long. Try
+ /* Loop through the instructions, classifying them as short/long. Try
to keep 2 short together and/or 1 long. Note, the ready list is
actually ordered backwards, so keep it in that manner. */
for (i = n_ready-1; i >= 0; i--)
@@ -2586,7 +2586,7 @@ conditional_move_operand (operand, mode)
if (mode != SImode && mode != HImode && mode != QImode)
return FALSE;
- /* At the moment we can hanndle moving registers and loading constants. */
+ /* At the moment we can handle moving registers and loading constants. */
/* To be added: Addition/subtraction/bitops/multiplication of registers. */
switch (GET_CODE (operand))
@@ -2728,7 +2728,7 @@ block_move_call (dest_reg, src_reg, bytes_rtx)
/* The maximum number of bytes to copy using pairs of load/store instructions.
If a block is larger than this then a loop will be generated to copy
- MAX_MOVE_BYTES chunks at a time. The value of 32 is a semi-arbitary choice.
+ MAX_MOVE_BYTES chunks at a time. The value of 32 is a semi-arbitrary choice.
A customer uses Dhrystome as their benchmark, and Dhrystone has a 31 byte
string copy in it. */
#define MAX_MOVE_BYTES 32
@@ -2788,7 +2788,7 @@ m32r_expand_block_move (operands)
/* If we are going to have to perform this loop more than
once, then generate a label and compute the address the
source register will contain upon completion of the final
- itteration. */
+ iteration. */
if (bytes > MAX_MOVE_BYTES)
{
final_src = gen_reg_rtx (Pmode);