<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED MOVED - Wayland lacks cross-process synchronisation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97353#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED MOVED - Wayland lacks cross-process synchronisation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97353">bug 97353</a>
from <span class="vcard"><a class="email" href="mailto:tomek.bury@gmail.com" title="Tomek Bury <tomek.bury@gmail.com>"> <span class="fn">Tomek Bury</span></a>
</span></b>
<pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=97353#c22">comment #22</a>)
<span class="quote">> (In reply to Tomek Bury from <a href="show_bug.cgi?id=97353#c20">comment #20</a>)
> > The eglWaitNative is a counterpart of eglWaitGL. It's only to synchronise
> > access form inside and outside GL(ES), not across processes.
>
> Specifically, this is wrong. eglWaitClient is glXWaitGL (note the reference
> to glFinish); eglWaitNative is glXWaitX.</span >
Yes, egl is more generic version of glX here. Still nothing says cross-process.
It only says GL and X draw commands, even if issued in a sequence from a single
thread aren't guaranteed to execute in that sequence, therefore explicit
synchronisation points are required. Also neither glX calls nor their EGL
counterpart imply blocking the calling thread, while glFinish does.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>