summaryrefslogtreecommitdiffstats
path: root/contrib/gcc/doc/md.texi
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/gcc/doc/md.texi')
-rw-r--r--contrib/gcc/doc/md.texi22
1 files changed, 11 insertions, 11 deletions
diff --git a/contrib/gcc/doc/md.texi b/contrib/gcc/doc/md.texi
index 6184fc3..822ec14 100644
--- a/contrib/gcc/doc/md.texi
+++ b/contrib/gcc/doc/md.texi
@@ -1,5 +1,5 @@
-@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1996, 1998, 1999, 2000, 2001, 2002
-@c Free Software Foundation, Inc.
+@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1996, 1998, 1999, 2000, 2001,
+@c 2002, 2003 Free Software Foundation, Inc.
@c This is part of the GCC manual.
@c For copying conditions, see the file gcc.texi.
@@ -5514,8 +5514,8 @@ in such processors and suggestions for their representation.
@cindex automaton based pipeline description
This section describes constructions of the automaton based processor
-pipeline description. The order of all mentioned below constructions
-in the machine description file is not important.
+pipeline description. The order of constructions within the machine
+description file is not important.
@findex define_automaton
@cindex pipeline hazard recognizer
@@ -5523,7 +5523,7 @@ The following optional construction describes names of automata
generated and used for the pipeline hazards recognition. Sometimes
the generated finite state automaton used by the pipeline hazard
recognizer is large. If we use more than one automaton and bind functional
-units to the automata, the summary size of the automata usually is
+units to the automata, the total size of the automata is usually
less than the size of the single automaton. If there is no one such
construction, only one finite state automaton is generated.
@@ -5533,12 +5533,12 @@ construction, only one finite state automaton is generated.
@var{automata-names} is a string giving names of the automata. The
names are separated by commas. All the automata should have unique names.
-The automaton name is used in construction @code{define_cpu_unit} and
+The automaton name is used in the constructions @code{define_cpu_unit} and
@code{define_query_cpu_unit}.
@findex define_cpu_unit
@cindex processor functional units
-Each processor functional unit used in description of instruction
+Each processor functional unit used in the description of instruction
reservations should be described by the following construction.
@smallexample
@@ -5599,7 +5599,7 @@ is negative, the cost is considered to be zero). You can always
change the default costs for any description by using the target hook
@code{TARGET_SCHED_ADJUST_COST} (@pxref{Scheduling}).
-@var{insn-names} is a string giving the internal name of the insn. The
+@var{insn-name} is a string giving the internal name of the insn. The
internal names are used in constructions @code{define_bypass} and in
the automaton description file generated for debugging. The internal
name has nothing in common with the names in @code{define_insn}. It is a
@@ -5685,7 +5685,7 @@ the common part by the following construction
@var{reservation-name} is a string giving name of @var{regexp}.
Functional unit names and reservation names are in the same name
space. So the reservation names should be different from the
-functional unit names and can not be reserved name @samp{nothing}.
+functional unit names and can not be the reserved name @samp{nothing}.
@findex define_bypass
@cindex instruction latency time
@@ -5772,8 +5772,8 @@ code. Currently there are the following options:
@itemize @bullet
@item
@dfn{no-minimization} makes no minimization of the automaton. This is
-only worth to do when we are going to query CPU functional unit
-reservations in an automaton state.
+only worth to do when we are debugging the description and need to
+look more accurately at reservations of states.
@item
@dfn{time} means printing additional time statistics about
OpenPOWER on IntegriCloud