※ 引述《ric2k1 (Ric)》之铭言：
: 4. For a gate 'k' in the original "watching-v/known" lists of 'g' (i.e. 'g'
: is one of the watch pointers of 'k'), 'k' will try to update its watch
: pointer. Generally, this update process may result in:
: (i) The watch pointer is successfully updated. Let the new watch
: pointer be 'p' with watch value 'u' (u = 0, 1, or known), the 'k'
: will be added to the "watching-u" list of gate 'p'.
: (ii) The watch pointer cannot be updated due to implication conflict
: in 'k' (i.e. all the pins on the gate have watch values.
: e.g. all the fanins of an OR gate have value '0' and the output has
: value '1'). Then 'k' will be restored back to the "watching-v/known"
: lists of 'g' and the conflict analysis process will be triggered.
: (iii) The watch pointer cannot be updated and neither new implication
: nor conflict is generated on 'k' (i.e. the other watch pointer has
: non-watch value). Then no action will be taken except that 'k' will
: be restored back to the "watching-v/known" lists of 'g'.
: Hope this is clear.
我想我大概知道怎么操作了
但是还是想知道哪种gate的哪种fan-in会在watching-known
而不是watching-0,1
另外,case(iii)是为了能detect未来的conflict吗?

Inputs and outputs of XOR gates

case (iii) 像是一个 OR gate output has value '0',the watch pointer (input) was implied from x to '0',and other fanins have already had values '0'跟 detect 未来的 conflict 无关

感谢回答,我想我应该懂了