[Bug 101572] glMemoryBarrier is backwards

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

 



Comment # 4 on bug 101572 from
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 from it, I could as well be telling the driver to do
both things at the same time.

I could see why unsetting the FBO would flush the necessary caches (due to
OpenGL guarantees, I'm saying "I'm done writing to this FBO" and now reads
should be guaranteed to be correct), so I'm going to take this for an answer.

I don't want to spend much more time on this matter either.

Thanks.


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