Changes between Version 75 and Version 76 of Orio

Timestamp:

06/14/08 16:40:00 (15 years ago)

Author:

hartono

Comment:

--

Orio

@@ -281 +281 @@
 In the earlier AXPY-4 case, one could view the module body block as redundant, since the annotation body already contains the same program. The motivation behind requiring Orio users to include the computation itself as part of the annotation is to avoid making use of a full-fledged C compiler infrastructure that potentially will compromise the simplicity, reliability, and portability of Orio. Furthermore, another reason is to allow the computation to be expressed by using domain-specific high-level languages, thus capturing the semantics without imposing tuning constraints resulting from the use of a general-purpose language.
 
-Below, we present a very simple example, which extends Orio with a new module that simply rewrites the annotated code without applying any code transformations at all. The new module has no parser component since there is no necessity to extract information from the annotated code, significantly simplifying the module implementation. First, we need to create a new subdirectory (with a name `simplyrewrite`, for instance) inside `src/module`. And then, we create an ''empty'' special file `__init__.py` inside directory `src/module/simplyrewrite`, so that Python will know that this folder is a package (i.e. a Python module). After that, a file named `simplyrewrite.py` that contains the implementation of the transformation module class must be defined in directory `src/module/simplyrewrite`. So, here is how the new directory structure will look like after applying the transformation module extension.
+Below, we present a very simple example, which extends Orio with a new module that simply rewrites the annotated code without applying any code transformations at all. The new module has no parser component since there is no necessity to extract information from the annotated code, significantly simplifying the module implementation. First, we need to create a new subdirectory (with a name `simplyrewrite`, for instance) inside `src/module`. And then, we create an ''empty'' special file `__init__.py` inside directory `src/module/simplyrewrite`, so that Python will know that this folder is a package (i.e. a Python module). After that, a file named `simplyrewrite.py` that contains the implementation of the transformation module class must be defined in directory `src/module/simplyrewrite`. So, here is how the new directory structure will look like after adding the new transformation module extension to Orio.
 
 {{{
@@ -298 +298 @@
 }}}
 
-And, below is the complete code of the `SimplyRewrite` class.
+And, below is the detailed code of the `SimplyRewrite` class.
 
 {{{
@@ -336 +336 @@
 }}}
 
+In the following sample, we show the input and output of the newly-added `SimplyRewrite` module.
+
+{{{
+% more simplyrewrite.py 
+/*@ begin SimplyRewrite (This is the module body code) @*/
+// This is the annotation body code
+/*@ end @*/
+
+% orcc simplyrewrite.py 
+
+% cat _simplyrewrite.py 
+/*@ begin SimplyRewrite (This is the module body code) @*/
+        /*
+         perf_params = {}
+         module_body_code = "This is the module body code"
+         annot_body_code = "
+// This is the annotation body code
+"
+         line_no = 1
+         indent_size = 0
+        */
+// This is the annotation body code
+/*@ end @*/
+}}}
+
 == More Detailed Documentation ==