Changes between Version 35 and Version 36 of Orio
- Timestamp:
- 06/11/08 21:30:27 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Orio
v35 v36 84 84 As previously discussed , Orio has two main functions: a ''source-to-source transformation tool'' and an ''automatic performance tuning tool''. In the following subsections, simple examples are provided to offer users the quickest way to begin using Orio. But first, a brief introduction to the annotation language syntax is presented next. 85 85 86 === Annotation Syntax ===86 === Annotation Language Syntax === 87 87 88 88 Orio annotation is denoted as a stylized C/C++ comment that starts with '`/*@`' and ends with `@*/`. For instance, the annotation `/*@ end @*/` is used to indicate the end of an annotated code region. The following simple grammar illustrates the fundamental structure of Orio annotations. … … 145 145 === Using Orio as an Automatic Performance Tool === 146 146 147 ''Under construction'' 147 148 148 == D ocumentations==149 == Developer Guide == 149 150 150 1. [wiki:Orio/CodeTransform Source-to-Source Transformation] 151 1. [wiki:Orio/PerfTuner Empirical Performance Tuning] 152 1. [wiki:Orio/ExtendOrio Extending Orio] 153 1. [wiki:Orio/PerfStudy Performance Study] 151 ''Under construction'' 154 152 155 153 == Papers == … … 157 155 * Boyana Norris, Albert Hartono, and William Gropp. "Annotations for Productivity and Performance Portability," in ''Petascale Computing: Algorithms and Applications''. Computational Science. Chapman & Hall / CRC Press, Taylor and Francis Group, 2007. Preprint ANL/MCS-P1392-0107. ([http://www-unix.mcs.anl.gov/~norris/new/all_bib.html#Norris:2007 bib], [http://www.mcs.anl.gov/uploads/mcs/papers/2007/P1392.pdf pdf]) 158 156 157 == Old Documentations (To be Removed) == 158 159 1. [wiki:Orio/PerfStudy Performance Study] 159 160 160 161