Fix classification of some microkernels

Author: jprotze

…rks/DRB129-mergeable-taskwait-orig-yes.c …arks/DRB129-mergeable-taskwait-orig-no.cmicro-benchmarks/DRB129-mergeable-taskwait-orig-yes.c renamed to micro-benchmarks/DRB129-mergeable-taskwait-orig-no.c micro-benchmarks/DRB129-mergeable-taskwait-orig-yes.c renamed to micro-benchmarks/DRB129-mergeable-taskwait-orig-no.c

@@ -15,7 +15,7 @@
  * variable.
  *
  * Implicit flush must be used after critical construct, after line:34 and before line:35 to avoid data race.
- * Data Race pair: x@34:9:W vs. x@34:9:W
+ * Data Race pair: x@34:9:W vs. x@43:11:R
  * */
 
 
@@ -39,9 +39,8 @@ int main(){
       while (tmp == 0) {
         #pragma omp atomic read acquire
         tmp = y;
-    }
-    #pragma omp critical
-    { if (x!=10) printf("x = %d\n", x); }
+      }
+      if (x!=10) printf("x = %d\n", x); 
     }
   }
   return 0;

micro-benchmarks/DRB142-acquirerelease-orig-yes.c

@@ -11,9 +11,13 @@
  * This is a program based on a dataset contributed by
  * Wenhao Wu and Stephen F. Siegel @Univ. of Delaware.
 
- * one synchronization commented out.
- * enters.  So race on x can occur.
- * Data race pair: x@104:9:W vs. x@111:9:W
+ * As soon as one thread releases all locks, the other thread can perform multiple
+ * barrier_wait() cycles ending up concurrent execution of different epochs. 
+ * Data race pair: x@108:9:W vs. x@115:9:W
+                   x@108:9:W vs. x@103:58:R
+                   x@108:9:W vs. x@110:58:R
+                   x@101:58:R vs. x@115:9:W
+                   x@110:58:R vs. x@115:9:W
  */
 
 #include <stdio.h>