Changes between Version 32 and Version 33 of OpenMPTransformation

Timestamp:

04/26/14 08:19:36 (12 years ago)

Author:

siegel

Comment:

--

OpenMPTransformation

@@ -119 +119 @@
  * of the top of the loop.  It is needed to check that all threads
  * encounter the same worksharing statements in the same order.
- * Parameter start is the initial value of the loop variable;
- * end is its final value; and inc is the increment (which can be
+ * The implementation will need the value start, the initial value of the loop variable;
+ * end is its final value; and inc, the increment (which can be
  * positive or negative).   These values can all be obtained by getting
  * the loop statement from the location and evaluating the expressions
@@ -382 +382 @@
 === Translating `atomic` ===
 
-This is just `$atomic`.  Or nothing, since assignment expressions are already atomic in CIVL-C.  The question is, what to do with non-atomic updates. They should register as race conditions.
+In general, reads and writes to shared variables will be processed using the protocols described above (dealing with state variables and ownership, etc.).  However if the operation occurs within an omp atomic construct, it is translated differently.
+
+If sequentially consistent atomic...
+
+If non-sequentially consistent atomic...
+
 
 ===  Translating`ordered` ===
@@ -414 +419 @@
     int i = info.iters[_i][0];
      ...
-      $when (order1==i) {
-        translate(S);
-        order1++;
-      }
+    $when (order1==i) {
+      translate(S1);
+      order1++;
+    }
       ...
-      $when (order2==i) {
-        translate(S2);
-        order2++;
-      }
+    $when (order2==i) {
+      translate(S2);
+      order2++;
+    }
       ...
   }