gfc-internals.texi: Fix typos.
* gfc-internals.texi: Fix typos. * simplify.c: Fix a comment typo. From-SVN: r123845
This commit is contained in:
parent
14463ee954
commit
71172460b6
|
@ -1,3 +1,8 @@
|
|||
2007-04-15 Kazu Hirata <kazu@codesourcery.com>
|
||||
|
||||
* gfc-internals.texi: Fix typos.
|
||||
* simplify.c: Fix a comment typo.
|
||||
|
||||
2007-04-14 Bernhard Fischer <aldot@gcc.gnu.org>
|
||||
|
||||
* primary.c: Commentary typo fix; Add question about redundant (?)
|
||||
|
|
|
@ -298,7 +298,7 @@ nested chain of @code{gfc_code} structures. The type of statement is
|
|||
identified by the @code{op} member of the structure, the different
|
||||
possible values are enumerated in @code{gfc_exec_op}. A special
|
||||
member of this @code{enum} is @code{EXEC_NOP} which is used to
|
||||
reperesent the various @code{END} statements if they carry a label.
|
||||
represent the various @code{END} statements if they carry a label.
|
||||
Depending on the type of statement some of the other fields will be
|
||||
filled in. Fields that are generally applicable are the @code{next}
|
||||
and @code{here} fields. The former points to the next statement in
|
||||
|
@ -314,7 +314,7 @@ block in question. The @code{SELECT} and @code{IF} statements may
|
|||
contain various blocks (the chain of @code{ELSE IF} and @code{ELSE}
|
||||
blocks or the various @code{CASE}s, respectively).
|
||||
|
||||
@c What would be nice here would be an example program togehter with
|
||||
@c What would be nice here would be an example program together with
|
||||
@c an image that says more than the mythical thousand words.
|
||||
|
||||
|
||||
|
|
|
@ -2842,7 +2842,7 @@ gfc_simplify_repeat (gfc_expr *e, gfc_expr *n)
|
|||
}
|
||||
mpz_clear (ncopies);
|
||||
|
||||
/* For further simplication, we need the character string to be
|
||||
/* For further simplification, we need the character string to be
|
||||
constant. */
|
||||
if (e->expr_type != EXPR_CONSTANT)
|
||||
return NULL;
|
||||
|
|
Loading…
Reference in New Issue