https://bugs.freedesktop.org/show_bug.cgi?id=101572
--- Comment #5 from Matias N. Goldberg ---
(btw unsetting the FBO indeed fixes the issue)
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=101572
--- Comment #4 from Matias N. Goldberg ---
After careful thought; I realized I don't need to switch to a dummy FBO; just
unset the current one.
That DOES make sense to me as while the FBO is bound and I'm executing the
compute shader that reads
https://bugs.freedesktop.org/show_bug.cgi?id=101572
--- Comment #3 from Matias N. Goldberg ---
I rather be told that I am wrong in how to interpret glMemoryBarrier, and that
I should be calling glMemoryBarrier( GL_FRAMEBUFFER_BARRIER_BIT ); because this
and that.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=101572
--- Comment #2 from Matias N. Goldberg ---
That can't be right.
You're suggesting that in order to synchronize writes from FBO with a Compute
Shader I am going to dispatch (which btw the Compute Shader is accessing this
fbo as a regular sample
https://bugs.freedesktop.org/show_bug.cgi?id=101572
Nicolai Hähnle changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101572
Bug ID: 101572
Summary: glMemoryBarrier is backwards
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: med
