We note that some common tricks, used to fool compilers into thinking that results are actually required, may fail in interpreted systems where optimisations can be performed at run time. For maximum portability, as well as ensuring adherence to standards, we have taken the decision to have no graphical component in the benchmark suite. While applets provide a convenient interface for running benchmarks on workstations and PCs, this is not true for typical supercomputers where interactive access may not be possible. For standardisation we have created a JGFBenchMark class to be used in all benchmark programs. This is described in detail in Section 3 .
Transparency is achieved by distributing the source code for all the benchmarks.