Re: [HACKERS] Weak-memory specific problem in ResetLatch/WaitLatch (follow-up analysis)

2012-03-25 Thread Michael Tautschnig
Hi, [...] > > Placing a sync (i.e., the strongest Power barrier) accordingly would, > > however, > > still be insufficient for the second problem, as it would only fix the > > reordering of read-read pairs by Worker 1 and the store atomicity issue from > > Worker 0. But the writes on Worker 0 cou

Re: [HACKERS] Weak-memory specific problem in ResetLatch/WaitLatch (follow-up analysis)

2012-03-24 Thread Michael Tautschnig
Hi again, [...] > > However, your example is enough unlike the actual code that the > conclusion you state following the word "clearly" isn't actually clear > to me. According to latch.h, the correct method of using a latch is > like this: > > * for (;;) > * { > * ResetLatch(); > *

[HACKERS] Weak-memory specific problem in ResetLatch/WaitLatch (follow-up analysis)

2012-02-29 Thread Michael Tautschnig
d like further discussion/validation of potential fixes! Best, Michael (on behalf of the team: Jade Alglave, Daniel Kroening, Vincent Nimal, Michael Tautschnig, as CC'ed) pgpplvVgeFxPl.pgp Description: PGP signature