[itanium-sched-branch] documentation clarification

[David Edelsohn]

	After discussing the unit to automata assigment constraint with
Vlad, he approved the following re-wording.

David


        * doc/md.texi: Clarify assignment of units to automata description.

Index: md.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/md.texi,v
retrieving revision 1.49.4.5
diff -c -p -r1.49.4.5 md.texi
*** md.texi	20 Dec 2002 21:08:55 -0000	1.49.4.5
--- md.texi	8 Jan 2003 20:30:58 -0000
*************** which the unit is bound.  The automaton 
*** 5488,5499 ****
  construction @code{define_automaton}.  You should give
  @dfn{automaton-name}, if there is a defined automaton.
  
! There are some constraints to assign units to automata.  The most
! important one is that, if a unit reservation is present on an
! alternative of a insn reservation on a given cycle, any unit from the
! same automaton should be also present on the rest alternatives of the
! reservation on the cycle.  The rest of the constraints are mentioned
! in the description of the subsequent constructions.
  
  @findex define_query_cpu_unit
  @cindex querying function unit reservations
--- 5488,5500 ----
  construction @code{define_automaton}.  You should give
  @dfn{automaton-name}, if there is a defined automaton.
  
! The assignment of units to automata are constrained by the uses of the
! units in insn reservations.  The most important constraint is: if a
! unit reservation is present on a particular cycle of an alternative
! for an insn reservation, then some unit from the same automaton must
! be present on the same cycle for the other alternatives of the insn
! reservation.  The rest of the constraints are mentioned in the
! description of the subsequent constructions.
  
  @findex define_query_cpu_unit
  @cindex querying function unit reservations