Lines Matching full:exists
87 20 exists (1:r0=1 /\ 1:r1=0)
158 Line 20 is the "exists" assertion expression to evaluate the final state.
174 The "exists" assertion on line 20 is satisfied if the consumer sees the
196 9 Condition exists (1:r0=1 /\ 1:r1=0)
202 indicates that the bad result flagged by the "exists" clause never
207 "exists" clause indicates a bad result. To see this, invert the "exists"
209 of this line indicate the number of end states satisfying the "exists"
222 "Never" on line 10, the state flagged by the "exists" clause is not
232 "No" says that the "exists" clause was not satisfied by any execution,
235 of end states satisfying and not satisfying the "exists" clause, just
236 like the two numbers at the end of line 10. Line 9 repeats the "exists"
277 23 exists (1:r0=1 /\ 1:r1=42)
280 means that the "exists" clause on line 23 must change "1:r1=0" to
294 9 Condition exists (1:r0=1 /\ 1:r1=42)
341 23 exists (0:r0=1 /\ 1:r0=1)
346 hope that the "exists" clause cannot be satisfied. LKMM agrees:
355 8 Condition exists (0:r0=1 /\ 1:r0=1)
380 in the "exists" clause. But sometimes debugging efforts are greatly
410 25 exists (0:r2=0 /\ 1:r4=0)
423 10 Condition exists (0:r2=0 /\ 1:r4=0)
434 "exists" clause. Someone modifying this test might wish to know the
464 26 exists (0:r2=0 /\ 1:r4=0)
477 10 Condition exists (0:r2=0 /\ 1:r4=0)
540 29 exists (0:r1=0 /\ 1:r1=0)
579 8 Condition exists (0:r1=0 /\ 1:r1=0)
589 possible "exists"-clause outcomes of program execution in the absence
597 Why not just add the "filter" clause to the "exists" clause, thus
601 fails to be satisfied. In contrast, the "exists" clause is evaluated
605 using the both the "filter" and "exists" clauses.
618 and static analysis that herd7 might do. Finally the "exists" clause
653 32 exists (x1=1)
666 7 Condition exists (x1=1)
711 25 exists (1:r0=x /\ 1:r1=0)
720 The "exists" clause works the same way, with the "1:r0=x" comparing P1()'s
722 "exists" clause therefore tests whether line 20's load from "y" saw the
745 8 Condition exists (1:r0=x /\ 1:r1=0)
755 scenario is flagged by the "exists" clause, and would occur if P1()
804 33 exists (* J *) (1:r0=x /\ (* K *) 1:r1=0) (* L *)
855 36 exists (0:r0=x /\ 0:r1=0)
900 instead causing it to focus solely on whether or not the "exists"
924 "exists" clause.