Mercurial > hg > truffle
changeset 2619:1586b1b56f0c
Fixed typo.
| author | Thomas Wuerthinger <thomas@wuerthinger.net> |
|---|---|
| date | Mon, 09 May 2011 19:12:45 +0200 |
| parents | 15774da89658 |
| children | a7ae14997372 |
| files | doc/design/graal_compiler.pdf doc/design/graal_compiler.tex |
| diffstat | 2 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/design/graal_compiler.tex Mon May 09 17:28:10 2011 +0200 +++ b/doc/design/graal_compiler.tex Mon May 09 19:12:45 2011 +0200 @@ -133,7 +133,7 @@ \item Nodes can have a control flow dependency, which means that the execution of one node will be followed by the execution of another node. This includes conditional execution, memory access serialization and other reasons, and again introduces a partial order to the set of nodes. \item Nodes can only have data and control dependencies to nodes which belong to the same graph. \item Control dependencies and data dependencies each represent a \emph{directed acyclic graph} (DAG) on the same set of nodes. This means that data dependencies always point upwards, and control dependencies always point downwards in a drawing of the graph. Situations that normally incur cycles (like loops) are represented by special nodes (see Section~\ref{sec:loops}). - \item Ordering between nodes is specified only to the extent which is required to correctly express the semantics of a given program. This gives the compiler flexibility for the possible scheduling of a node and therefore wriggle room for optimizations. For algorithms that require a fixed ordering of nodes, a temporary schedule can always be generated. + \item Ordering between nodes is specified only to the extent which is required to correctly express the semantics of a given program. This gives the compiler flexibility for the possible scheduling of a node and therefore wiggle room for optimizations. For algorithms that require a fixed ordering of nodes, a temporary schedule can always be generated. \item Both data and control dependencies can be traversed in both directions, so that each node can be traversed in four directions (see Figure~\ref{fig:directions}): \begin{itemize} \item \emph{inputs} are all nodes that this node has data dependencies on.