[concurrency-interest] The very best CAS loop

Andrew Haley aph at redhat.com
Thu Sep 29 04:36:53 EDT 2016

On 28/09/16 18:55, Andrew Haley wrote:
> The only really likely explanation for that is that the thread is
> descheduled or otherwise interrupted by the OS kernel and this
> obviously would cause a weak CAS to fail.

Oh, silly me!  This is a deoptimization trap, of course.


More information about the Concurrency-interest mailing list