next up previous
Next: Optimization Strategies Up: Case Study 1: Matrix Previous: HPJava Language Featues


Translation

Figure 3: Naive translation of nested overall loops from Figure 1.

\begin{displaymath}
\begin{minipage}[t]{\linewidth}\small\begin{tabbing}
\verb$i...
...ert }\vert \\
\verb\vert}\vert \\
\end{tabbing}\end{minipage}\end{displaymath}

In stark distinction to HPF, the HPJava translation scheme does not require insertion of compiler-generated communications, making it relatively straightforward. The most complicated part is ensuring that node code works independently of the distribution format of arrays. The current translation schemes is documented in detail in the HPJava manual [3] and translation scheme [1].

Figure 3 gives the translation of the ``loop nest'' from Figure 1--the two overall constructs with included for loop. Apart from cosmetic whitespace, and renaming of compiler-generated temporary names to the more readable form $t_i$, this is the actual code emitted by the current version of the translator.



Bryan Carpenter 2004-04-24