[cairo-bugs] [Bug 103037] Segmentation fault in _cairo_traps_compositor_glyphs

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 9 22:20:59 UTC 2017


--- Comment #18 from Mikhail Fludkov <fludkov.me at gmail.com> ---
http://en.cppreference.com/w/c/atomic/memory_order makes me think I'm mistaken.
everywhere I used memory_order_seq_cst, can be replaced with
memory_order_release. Because:
memory_order_release - All writes in the current thread are visible in other
threads that acquire the same atomic variable
memory_order_acquire - All writes in other threads that release the same atomic
variable are visible in the current thread

It is very hard to wrap my head around the topic. I think we are still fine
with the patch as all the operations (load/store/cmp_exchg) used in the patch
have the strongest semantic (memory_order_seq_cst).

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cairographics.org/archives/cairo-bugs/attachments/20171009/729562fb/attachment.html>

More information about the cairo-bugs mailing list