Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 03/06/2025, 09:24:06 UTC
Writing a value involves reading the value.
Since each thread is just a sequence of instructions. We can log each step of its insertion way and compare the results afterwards.

Yeah, but those instructions run in parallel, hence it's guaranteed that, without an access sync, at some point, a r/w race condition will occur. You should know best what'ya doin', so I won't insist.
Or are you saying this can never happen:

Code:
X = 0

Cycle T0          T1
0      read X .  read X      // T0: is X 0 or 32? T1: is X 0 or 8?
1      set x[3] set X[5] .   // T0: is X 8 or 40? T1: is X 32 or 40?
2     write X  write X . write X      // what X is final? what about cache lines refresh?
3 .    X = ????????           // one of 8, 32, or 40
Original archived Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Scraped on 03/06/2025, 09:19:06 UTC
Writing a value involves reading the value.
Since each thread is just a sequence of instructions. We can log each step of its insertion way and compare the results afterwards.

Yeah, but those instructions run in parallel, hence it's guaranteed that, without an access sync, at some point, a r/w race condition will occur. You should know best what'ya doin', so I won't insist.
Or are you saying this can never happen:

Code:
X = 0

Cycle T0         T1
0     read X.  read X      // T0: is X 0 or 32 ? T1: is X 0 or 8?
1     set x[3] set X[5].   // T0: is X 8 or 40? T1: is X 32 or 40?
2     write X. write X      // what X is final? what about cache lines refresh?
3.    X = ????????          // one of 8, 32, or 40