[Bug 101572] glMemoryBarrier is backwards

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



changed bug 101572
What Removed Added
Status NEW RESOLVED
Resolution --- NOTOURBUG

Comment # 1 on bug 101572 from
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:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux