* doc/c-alpha.texi: Fix typos.

* doc/c-ia64.texi: Likewise.
	* doc/c-mmix.texi: Likewise.
	* doc/c-sh64.texi: Likewise.
	* doc/c-xtensa.texi: Likewise.
	* doc/internals.texi: Likewise.
This commit is contained in:
Kazu Hirata 2003-10-26 18:12:03 +00:00
parent 3e685d417e
commit 6049379740
7 changed files with 24 additions and 15 deletions

View File

@ -1,3 +1,12 @@
2003-10-26 Kazu Hirata <kazu@cs.umass.edu>
* doc/c-alpha.texi: Fix typos.
* doc/c-ia64.texi: Likewise.
* doc/c-mmix.texi: Likewise.
* doc/c-sh64.texi: Likewise.
* doc/c-xtensa.texi: Likewise.
* doc/internals.texi: Likewise.
2003-10-24 H.J. Lu <hongjiu.lu@intel.com>
* config/obj-elf.c (obj_elf_change_section): Allow SHF_ALLOC

View File

@ -139,12 +139,12 @@ OpenVMS syntax, with a few differences for ELF.
@cindex Alpha registers
@cindex register names, Alpha
The 32 integer registers are refered to as @samp{$@var{n}} or
The 32 integer registers are referred to as @samp{$@var{n}} or
@samp{$r@var{n}}. In addition, registers 15, 28, 29, and 30 may
be refered to by the symbols @samp{$fp}, @samp{$at}, @samp{$gp},
be referred to by the symbols @samp{$fp}, @samp{$at}, @samp{$gp},
and @samp{$sp} respectively.
The 32 floating-point registers are refered to as @samp{$f@var{n}}.
The 32 floating-point registers are referred to as @samp{$f@var{n}}.
@node Alpha-Relocs
@subsection Relocations
@ -153,7 +153,7 @@ The 32 floating-point registers are refered to as @samp{$f@var{n}}.
Some of these relocations are available for ECOFF, but mostly
only for ELF. They are modeled after the relocation format
introduced in Digial Unix 4.0, but there are additions.
introduced in Digital Unix 4.0, but there are additions.
The format is @samp{!@var{tag}} or @samp{!@var{tag}!@var{number}}
where @var{tag} is the name of the relocation. In some cases

View File

@ -110,12 +110,12 @@ Reference Guide.
@cindex IA-64 registers
@cindex register names, IA-64
The 128 integer registers are refered to as @samp{r@var{n}}.
The 128 floating-point registers are refered to as @samp{f@var{n}}.
The 128 application registers are refered to as @samp{ar@var{n}}.
The 128 control registers are refered to as @samp{cr@var{n}}.
The 64 one-bit predicate registers are refered to as @samp{p@var{n}}.
The 8 branch registers are refered to as @samp{b@var{n}}.
The 128 integer registers are referred to as @samp{r@var{n}}.
The 128 floating-point registers are referred to as @samp{f@var{n}}.
The 128 application registers are referred to as @samp{ar@var{n}}.
The 128 control registers are referred to as @samp{cr@var{n}}.
The 64 one-bit predicate registers are referred to as @samp{p@var{n}}.
The 8 branch registers are referred to as @samp{b@var{n}}.
In addition, the assembler defines a number of aliases:
@samp{gp} (@samp{r1}), @samp{sp} (@samp{r12}), @samp{rp} (@samp{b0}),
@samp{ret0} (@samp{r8}), @samp{ret1} (@samp{r9}), @samp{ret2} (@samp{r10}),

View File

@ -443,7 +443,7 @@ operand can be omitted, defaulting to a zero value.
The directives @samp{WYDE}, @samp{TETRA} and @samp{OCTA} emit constants of
two, four and eight bytes size respectively. Before anything else happens
for the directive, the current location is aligned to the respective
constant-size bondary. If a label is defined at the beginning of the
constant-size boundary. If a label is defined at the beginning of the
line, its value will be that after the alignment. A single operand can be
omitted, defaulting to a zero value emitted for the directive. Operands
can be expressed as strings (@pxref{Strings}), in which case each

View File

@ -173,7 +173,7 @@ this directive unless you specified an ABI on the command line, and the
ABIs specified must match.
@item .uaquad
Like .uaword and .ualong, this allows you to specify an intenionally
Like .uaword and .ualong, this allows you to specify an intensionally
unaligned quadword (64 bit word).
@end table

View File

@ -213,7 +213,7 @@ opcodes (@pxref{Xtensa Opcodes, ,Opcode Names}), by using the
Line Options}), or by using the @code{no-density} directive
(@pxref{Density Directive, ,density}).
It is a good idea @emph{not} to use the density instuctions directly.
It is a good idea @emph{not} to use the density instructions directly.
The assembler will automatically select dense instructions where
possible. If you later need to avoid using the code density option, you
can disable it in the assembler without having to modify the code.
@ -351,7 +351,7 @@ range, function call relaxation can be enabled using the
@cindex relaxation of @code{MOVI} instructions
The @code{MOVI} machine instruction can only materialize values in the
range from -2048 to 2047. Values outside this range are best
materalized with @code{L32R} instructions. Thus:
materialized with @code{L32R} instructions. Thus:
@smallexample
movi a0, 100000

View File

@ -1740,7 +1740,7 @@ Usually, if the symbol is in the same section as the frag (given by the
@var{sec} argument), the narrowest likely relaxation mode is stored in
@code{fr_subtype}, and that's that.
If the symbol is undefined, or in a different section (and therefore moveable
If the symbol is undefined, or in a different section (and therefore movable
to an arbitrarily large distance), the largest available relaxation mode is
specified, @code{fix_new} is called to produce the relocation record,
@code{fr_fix} is increased to include the relocated field (remember, this