[concurrency-interest] The very best CAS loop

Andrew Haley aph at redhat.com
Tue Sep 27 15:25:15 EDT 2016

On 27/09/16 19:18, Martin Buchholz wrote:

> My proposal produces strictly cleaner, more compact source code and
> bytecode, while maintaining the property that updateFunction will
> never be called just because of a spurious weak cas failure, without
> loss of performance, so ... COMMIT IS YES?

I don't think so, for reasons discussed.


More information about the Concurrency-interest mailing list