Changes between Version 42 and Version 43 of Orio

Timestamp:

06/12/08 03:26:54 (15 years ago)

Author:

hartono

Comment:

--

Orio

@@ -190 +190 @@
  * ''input_vars'': to specify both the declarations and the initializations of the input variables
 
-So in this example, the transformed AXPY-4 code is compiled using GCC compiler with the -O3 option to activate all its optimizations. The unroll factor values under consideration extends over integers from 1 to 32, inclusively. The AXPY-4 computation is tuned for two distinct problem sizes: N=1K and N=10M. Also, all scalars and arrays involved in the computation must be declared and initialized in the tuning specifications to enable the performance testing driver to empirically execute the optimized code.  It is to be noted that the ''static'' and ''dynamic'' keywords provide guidance to the performance testing driver as it allocates memory space for the declared arrays.
-
--- output files???
+So in this example, the transformed AXPY-4 code is compiled using GCC compiler with the -O3 option to activate all its optimizations. The unroll factor values under consideration extends over integers from 1 to 32, inclusively. The AXPY-4 computation is tuned for two distinct problem sizes: N=1K and N=10M. Also, all scalars and arrays involved in the computation must be declared and initialized in the tuning specifications to enable the performance testing driver to empirically execute the optimized code.  It is to be noted that the ''static'' and ''dynamic'' keywords provide guidance to the performance testing driver on how it should allocate memory space for the declared arrays.
+
+Provided the fact that performance tuning is performed for each different problem size, the number of generated programs is therefore equivalent to the number of distinct combinations of input problem sizes. So, there are two generated program outputs for the AXPY-4 example. Using the default file naming convention, `_axpy_N_1000.c` and `_axpy_N_10000000.c` output files represent the products of Orio optimization process for input sizes N=1K and N=10M, respectively.
 
 === Using Different Search Space Exploration Strategies ===
 
-Due to the huge search space of the parameter values, a proper search heuristic becomes a critical component of an empirical tuning system. Hence, in addition to an exhaustive search and a random search, two effective and practical search heuristic strategies have been developed and integrated into the Orio’s search engine. These heuristics include the ''Nelder-Mead Simplex'' method and ''Simulated Annealing'' method.
+Due to the huge search space of the parameter values, a proper search heuristic becomes a critical component of an empirical tuning system. Hence, in addition to an ''exhaustive search'' and a ''random search'', two effective and practical search heuristic strategies have been developed and integrated into the Orio’s search engine. These heuristics include the ''Nelder-Mead Simplex'' method and ''Simulated Annealing'' method. 
 
 ''Under construction''