execution: bugfix - resolved promises should propagate synchronization
authorBrian Norris <banorris@uci.edu>
Wed, 8 May 2013 17:09:52 +0000 (10:09 -0700)
committerBrian Norris <banorris@uci.edu>
Wed, 8 May 2013 17:09:52 +0000 (10:09 -0700)
A new write ModelAction may resolve a Promise, completing a release
sequence and updating the read's clock vector. This update should be
propagated to any ModelAction later in the execution order which had
previously "happened after" the read.


No differences found