Searched refs:outcome (Results 1 – 6 of 6) sorted by relevance
53 if test "$outcome" = DEADLOCK59 echo " !!! Unexpected non-$outcome verification" $litmus62 echo " !!! Unexpected non-$outcome verification" >> $LKMM_DESTDIR/$litmus.out 2>&166 elif grep '^Observation' $LKMM_DESTDIR/$litmus.out | grep -q $outcome || test "$outcome" = Maybe70 echo " !!! Unexpected non-$outcome verification" $litmus73 echo " !!! Unexpected non-$outcome verification" >> $LKMM_DESTDIR/$litmus.out 2>&1
6 * Can the counter-intuitive message-passing outcome be prevented with
6 * Can the counter-intuitive outcome for the load-buffering pattern
155 value of r1 be 0. The reason for this surprising outcome is that188 sufficiently to rule out the counter-intuitive outcome.206 outcome in which the first load sees the value written by the second store360 One way of avoiding the counter-intuitive outcome is through the use of a401 the counter-intuitive outcome where the kernel overwrites the data496 this counter-intuitive outcome.517 "if (@cond)". The full barriers prevent the undesirable outcome where550 avoid a counter-intuitive outcome depends on the types of relations551 linking the memory accesses for the outcome in question:
175 happens, the LKMM does predict this outcome can occur, and the example210 execute before itself, the specified outcome is impossible.219 Ordering). This model predicts that the undesired outcome for the MP243 Sequential Consistency predicts that the outcome r0 = 0, r1 = 0 is245 this outcome to occur, and in fact it does sometimes occur on x86 and277 and a certain outcome for the loads in a piece of code can happen only279 that outcome cannot occur.1293 outcome is impossible -- as it should be.1421 prevents the r0 = 0, r1 = 0 outcome.1682 forbidden cycle, violating the "rcu" axiom. Hence the outcome is not[all …]
104 the outcome nicely.