extend.texi, [...]: Fix typos.
* doc/extend.texi, doc/gimple.texi, doc/invoke.texi, doc/md.texi, doc/sourcebuild.texi, doc/tm.texi: Fix typos. Follow spelling conventions. From-SVN: r143481
This commit is contained in:
parent
dba2cc0ce9
commit
a640c13b6b
@ -1,3 +1,9 @@
|
||||
2009-01-18 Kazu Hirata <kazu@codesourcery.com>
|
||||
|
||||
* doc/extend.texi, doc/gimple.texi, doc/invoke.texi,
|
||||
doc/md.texi, doc/sourcebuild.texi, doc/tm.texi: Fix typos.
|
||||
Follow spelling conventions.
|
||||
|
||||
2009-01-18 Ben Elliston <bje@au.ibm.com>
|
||||
|
||||
* bitmap.c (bitmap_obstack_alloc_stat): Adjust cast to eliminate
|
||||
|
@ -2782,7 +2782,7 @@ with modern codes that keep a 16-byte stack for SSE compatibility.
|
||||
@cindex @code{resbank} attribute
|
||||
On the SH2A target, this attribute enables the high-speed register
|
||||
saving and restoration using a register bank for @code{interrupt_handler}
|
||||
routines. Saving to the bank is performed automatcially after the CPU
|
||||
routines. Saving to the bank is performed automatically after the CPU
|
||||
accepts an interrupt that uses a register bank.
|
||||
|
||||
The nineteen 32-bit registers comprising general register R0 to R14,
|
||||
|
@ -109,7 +109,7 @@ structure takes 4 words (32 bytes) on 64 bit hosts:
|
||||
@item @code{visited} @tab 1
|
||||
@item @code{nontemporal_move} @tab 1
|
||||
@item @code{plf} @tab 2
|
||||
@item @code{modifed} @tab 1
|
||||
@item @code{modified} @tab 1
|
||||
@item @code{has_volatile_ops} @tab 1
|
||||
@item @code{references_memory_p} @tab 1
|
||||
@item @code{uid} @tab 32
|
||||
|
@ -1387,14 +1387,14 @@ is currently only supported when compiling C or C++.
|
||||
|
||||
The compiler can accept several base standards, such as @samp{c89} or
|
||||
@samp{c++98}, and GNU dialects of those standards, such as
|
||||
@samp{gnu89} or @samp{gnu++98}. By specifing a base standard, the
|
||||
@samp{gnu89} or @samp{gnu++98}. By specifying a base standard, the
|
||||
compiler will accept all programs following that standard and those
|
||||
using GNU extensions that do not contradict it. For example,
|
||||
@samp{-std=c89} turns off certain features of GCC that are
|
||||
incompatible with ISO C90, such as the @code{asm} and @code{typeof}
|
||||
keywords, but not other GNU extensions that do not have a meaning in
|
||||
ISO C90, such as omitting the middle term of a @code{?:}
|
||||
expression. On the other hand, by specifing a GNU dialect of a
|
||||
expression. On the other hand, by specifying a GNU dialect of a
|
||||
standard, all features the compiler support are enabled, even when
|
||||
those features change the meaning of the base standard and some
|
||||
strict-conforming programs may be rejected. The particular standard
|
||||
@ -6605,7 +6605,7 @@ compiling and when linking your program.
|
||||
The following options are enabled: @code{-fprofile-arcs}, @code{-fprofile-values}, @code{-fvpt}.
|
||||
|
||||
If @var{path} is specified, GCC will look at the @var{path} to find
|
||||
the profile feeedback data files. See @option{-fprofile-dir}.
|
||||
the profile feedback data files. See @option{-fprofile-dir}.
|
||||
|
||||
@item -fprofile-use
|
||||
@itemx -fprofile-use=@var{path}
|
||||
@ -7601,8 +7601,8 @@ optimizing at @option{-O3} and above. For some sorts of source code
|
||||
the enhanced partial redundancy elimination optimization can run away,
|
||||
consuming all of the memory available on the host machine. This
|
||||
parameter sets a limit on the length of the sets that are computed,
|
||||
which prevents the runaway behaviour. Setting a value of 0 for
|
||||
this paramter will allow an unlimited set length.
|
||||
which prevents the runaway behavior. Setting a value of 0 for
|
||||
this parameter will allow an unlimited set length.
|
||||
|
||||
@item sccvn-max-scc-size
|
||||
Maximum size of a strongly connected component (SCC) during SCCVN
|
||||
@ -9077,7 +9077,7 @@ best available method for the selected processor. The default setting is
|
||||
Only generate absolute relocations on word sized values (i.e. R_ARM_ABS32).
|
||||
This is enabled by default on targets (uClinux, SymbianOS) where the runtime
|
||||
loader imposes this restriction, and when @option{-fpic} or @option{-fPIC}
|
||||
is speficied.
|
||||
is specified.
|
||||
|
||||
@end table
|
||||
|
||||
@ -13317,7 +13317,7 @@ Disables warnings about the generation of inefficient code. These
|
||||
warnings can be generated, for example, when compiling code which
|
||||
performs byte-level memory operations on the MAC AE type. The MAC AE has
|
||||
no hardware support for byte-level memory operations, so all byte
|
||||
load/stores must be synthesised from word load/store operations. This is
|
||||
load/stores must be synthesized from word load/store operations. This is
|
||||
inefficient and a warning will be generated indicating to the programmer
|
||||
that they should rewrite the code to avoid byte operations, or to target
|
||||
an AE type which has the necessary hardware support. This option enables
|
||||
|
@ -3149,7 +3149,7 @@ A definition of another insn attribute used to describe for what
|
||||
reason an insn alternative might be available or
|
||||
not. E.g. @code{cpu_facility} as in the example below.
|
||||
@item
|
||||
An assignement for the second attribute to each insn definition
|
||||
An assignment for the second attribute to each insn definition
|
||||
combining instructions which are not all available under the same
|
||||
circumstances. (Note: It obviously only makes sense for definitions
|
||||
with more than one alternative. Otherwise the insn pattern should be
|
||||
|
@ -1575,7 +1575,7 @@ Finalize use of torture lists.
|
||||
@end table
|
||||
|
||||
The @file{.exp} file for a set of tests that use torture options must
|
||||
include calls to these three procecures if:
|
||||
include calls to these three procedures if:
|
||||
|
||||
@itemize @bullet
|
||||
@item It calls @code{gcc-dg-runtest} and overrides @var{DG_TORTURE_OPTIONS}.
|
||||
|
@ -6386,7 +6386,7 @@ Return a pointer to a store large enough to hold target scheduling context.
|
||||
@deftypefn {Target Hook} void TARGET_SCHED_INIT_SCHED_CONTEXT (void *@var{tc}, bool @var{clean_p})
|
||||
Initialize store pointed to by @var{tc} to hold target scheduling context.
|
||||
It @var{clean_p} is true then initialize @var{tc} as if scheduler is at the
|
||||
beginning of the block. Overwise, make a copy of the current context in
|
||||
beginning of the block. Otherwise, make a copy of the current context in
|
||||
@var{tc}.
|
||||
@end deftypefn
|
||||
|
||||
@ -6409,7 +6409,7 @@ Return a pointer to a store large enough to hold target scheduling context.
|
||||
@deftypefn {Target Hook} void TARGET_SCHED_INIT_SCHED_CONTEXT (void *@var{tc}, bool @var{clean_p})
|
||||
Initialize store pointed to by @var{tc} to hold target scheduling context.
|
||||
It @var{clean_p} is true then initialize @var{tc} as if scheduler is at the
|
||||
beginning of the block. Overwise, make a copy of the current context in
|
||||
beginning of the block. Otherwise, make a copy of the current context in
|
||||
@var{tc}.
|
||||
@end deftypefn
|
||||
|
||||
@ -9365,7 +9365,7 @@ For targets whose psABI does not provide Thread Local Storage via
|
||||
specific relocations and instruction sequences, an emulation layer is
|
||||
used. A set of target hooks allows this emulation layer to be
|
||||
configured for the requirements of a particular target. For instance
|
||||
the psABI may infact specify TLS support in terms of an emulation
|
||||
the psABI may in fact specify TLS support in terms of an emulation
|
||||
layer.
|
||||
|
||||
The emulation layer works by creating a control object for every TLS
|
||||
|
Loading…
Reference in New Issue
Block a user