1*4882a593SmuzhiyunC LB+poonceonces 2*4882a593Smuzhiyun 3*4882a593Smuzhiyun(* 4*4882a593Smuzhiyun * Result: Sometimes 5*4882a593Smuzhiyun * 6*4882a593Smuzhiyun * Can the counter-intuitive outcome for the load-buffering pattern 7*4882a593Smuzhiyun * be prevented even with no explicit ordering? 8*4882a593Smuzhiyun *) 9*4882a593Smuzhiyun 10*4882a593Smuzhiyun{} 11*4882a593Smuzhiyun 12*4882a593SmuzhiyunP0(int *x, int *y) 13*4882a593Smuzhiyun{ 14*4882a593Smuzhiyun int r0; 15*4882a593Smuzhiyun 16*4882a593Smuzhiyun r0 = READ_ONCE(*x); 17*4882a593Smuzhiyun WRITE_ONCE(*y, 1); 18*4882a593Smuzhiyun} 19*4882a593Smuzhiyun 20*4882a593SmuzhiyunP1(int *x, int *y) 21*4882a593Smuzhiyun{ 22*4882a593Smuzhiyun int r0; 23*4882a593Smuzhiyun 24*4882a593Smuzhiyun r0 = READ_ONCE(*y); 25*4882a593Smuzhiyun WRITE_ONCE(*x, 1); 26*4882a593Smuzhiyun} 27*4882a593Smuzhiyun 28*4882a593Smuzhiyunexists (0:r0=1 /\ 1:r0=1) 29