This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

pipeline docs patch

The following patch clarifies some of the language in the automaton
pipeline description.  There is more work to be done, but this is a
start.  Okay to commit?


2003-05-14  Ben Elliston  <>

	* doc/md.texi (Automaton pipeline description): Grammar fixes.

Index: md.texi
RCS file: /cvs/gcc/gcc/gcc/doc/md.texi,v
retrieving revision 1.66
diff -u -r1.66 md.texi
--- md.texi	10 May 2003 22:59:04 -0000	1.66
+++ md.texi	14 May 2003 01:46:54 -0000
@@ -5600,8 +5600,8 @@
 @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
@@ -5609,7 +5609,7 @@
 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.
@@ -5619,12 +5619,12 @@
 @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
 @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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]