[Bug 101572] glMemoryBarrier is backwards

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

 



Comment # 2 on bug 101572 from
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 fetch, not via imageLoad/imageStore) then I either need
to:

1. Switch to a dummy FBO, something that is mentioned nowhere: neither on
manuals or online documentation, wikis, or tutorials; also it's not mentioned
to be a guarantee in the spec either.

2. Use a function that was added in OpenGL 4.5; when Compute Shaders were added
in 4.3.

I may be misinterpreting the spec; but these solution don't make any sense.
Best case Mesa should detect that I am trying to read from an FBO in a compute
shader being dispatched and issue a barrier for me; worst case one of the
functionality already present in 4.3 (like glMemoryBarrier) that doesn't look
esoteric (like switching FBOs) should be enough to synchronize.


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