[Bug 101572] glMemoryBarrier is backwards
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jun 27 09:12:10 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=101572
Nicolai Hähnle <nhaehnle at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #1 from Nicolai Hähnle <nhaehnle at gmail.com> ---
You're misinterpreting the spec.
glMemoryBarrier ensures that **writes from shaders** are visible to whatever
consumer you indicate with the given flag bits.
What you seem to be trying to do is ensure that **writes via the framebuffer**
are visible in subsequent compute shader invocations. For that, you need to
either:
(1) Bind a different framebuffer, or (probably more appropriate to what you're
trying to do)
(2) use glTextureBarrier.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170627/f8568866/attachment.html>
More information about the dri-devel
mailing list