Changes between Version 33 and Version 34 of Orio

Timestamp:

06/11/08 20:41:53 (15 years ago)

Author:

hartono

Comment:

--

Orio

@@ -86 +86 @@
 === Annotation Syntax ===
 
-Orio annotation is denoted as a stylized C/C++ comment that starts with `/*@` and ends with `@*/`. For instance, the annotation `/*@ end @*/`, called ''trailer annotation'', is used to indicate the end of an annotated code region. The following simple grammar illustrates the fundamental structure of Orio annotations.
+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.
 
   <annotation-region> ::= <leader-annotation> <annotation-body> <trailer-annotation> [[BR]]
@@ -92 +92 @@
   <trailer-annotation> ::= `/*@ end @*/` [[BR]]
 
-An ''annotation region'' consists of three main parts: ''leader annotation'', ''annotation body'', and ''trailer annotation''. The annotation body can either be empty or contain C/C++ code that may include other nested annotation regions. A leader annotation contains the ''module name'' of the code transformation component that is loaded dynamically by Orio. A high level abstraction of the computation and the performance hints are coded in the ''module body'' inside the leader annotation and are used as input by the transformation module during the transformation and code generation phases. A trailer annotation has a fixed form to close the annotation region.
+An ''annotation region'' consists of three main parts: ''leader annotation'', ''annotation body'', and ''trailer annotation''. The annotation body can either be empty or contain C/C++ code that may include other nested annotation regions. A leader annotation contains the ''module name'' of the code transformation component that is loaded dynamically by Orio. A high level abstraction of the computation and the performance hints are coded in the ''module body'' inside the leader annotation and are used as input by the transformation module during the transformation and code generation phases. A trailer annotation, which has a fixed form (i.e. `/*@ end @*/`), closes an annotation region.
 
 === Using Orio as a Source-to-Source Code Transformation Tool ===
@@ -115 +115 @@
 }}}
 
-By default, the transformed output code is written to the file `_axpy4.c`. Optionally, users can specify the name of the output file using the command option '`-o <file>`'. Below is how the output code looks like.
+By default, the transformed output code is written to the file `_axpy4.c`. Optionally, users can specify the name of the output file using the command option `-o <file>`. Below is how the output code looks like.
 
 {{{