Re: [PATCH 1/1] gdiplus: Use atomic write for releasing GpImage lock.

[Zebediah Figura]

On 10/4/22 10:36, Jin-oh Kang wrote:
> > Why does this need release semantics,
>
> This function can be inlined, and the write to `busy` can be reordered
> before any other operations.

Well, sure, but why is that a problem?
> and where is the corresponding
> > acquire?
>
> In image_lock's `InterlockedCompareExchange(&image->busy, ...)`

The point is that both of these questions should be clearly answered in 
the patch itself :-)