search for: arb_shader_storage_buffer_object

...> Are you sure this won't break compute shaders on fermi? > Could you please double-check that? I just checked: lspci: 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) Before this patch-set: [hans at plank piglit]$ ./piglit run -o shader -t '.*arb_shader_storage_buffer_object.*' results/shader [9/9] pass: 9 / After this patch-set: [hans at plank piglit]$ ./piglit run -o shader -t '.*arb_shader_storage_buffer_object.*' results/shader [9/9] pass: 9 / > One minor comment below. > > On 03/17/2016 05:07 PM, Hans de Goede wrote: >> Some of the lo...

...check that? >> >> I just checked: >> >> lspci: >> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT >> 610] (rev a1) >> >> Before this patch-set: >> >> [hans at plank piglit]$ ./piglit run -o shader -t >> '.*arb_shader_storage_buffer_object.*' results/shader >> [9/9] pass: 9 / >> >> After this patch-set: >> >> [hans at plank piglit]$ ./piglit run -o shader -t >> '.*arb_shader_storage_buffer_object.*' results/shader >> [9/9] pass: 9 / > > And what about compute shaders? (ie. -...

...on fermi? >> Could you please double-check that? > > I just checked: > > lspci: > 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT > 610] (rev a1) > > Before this patch-set: > > [hans at plank piglit]$ ./piglit run -o shader -t > '.*arb_shader_storage_buffer_object.*' results/shader > [9/9] pass: 9 / > > After this patch-set: > > [hans at plank piglit]$ ./piglit run -o shader -t > '.*arb_shader_storage_buffer_object.*' results/shader > [9/9] pass: 9 / And what about compute shaders? (ie. -t arb_compute_shader) Sorry to ask yo...

...checked: >>> >>> lspci: >>> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT >>> 610] (rev a1) >>> >>> Before this patch-set: >>> >>> [hans at plank piglit]$ ./piglit run -o shader -t >>> '.*arb_shader_storage_buffer_object.*' results/shader >>> [9/9] pass: 9 / >>> >>> After this patch-set: >>> >>> [hans at plank piglit]$ ./piglit run -o shader -t >>> '.*arb_shader_storage_buffer_object.*' results/shader >>> [9/9] pass: 9 / >> >> An...

...se FILE_MEMORY_BUFFER at the ir_from_tgsi and lowering steps, freeing use of FILE_MEMORY_GLOBAL for use with OpenCL global buffers. Note that after lowering buffer accesses use the FILE_MEMORY_GLOBAL register file. Tested with piglet on a gk107, before this patch: ./piglit run -o shader -t '.*arb_shader_storage_buffer_object.*' results/shader [9/9] pass: 9 / after: ./piglit run -o shader -t '.*arb_shader_storage_buffer_object.*' results/shader [9/9] pass: 9 / Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- Changes in v2: -New patch in v2 of patch-set to re-enable support for global opencl b...

...rom_tgsi and lowering steps, freeing use of FILE_MEMORY_GLOBAL > for use with OpenCL global buffers. > > Note that after lowering buffer accesses use the FILE_MEMORY_GLOBAL > register file. > > Tested with piglet on a gk107, before this patch: > ./piglit run -o shader -t '.*arb_shader_storage_buffer_object.*' results/shader > [9/9] pass: 9 / > after: > ./piglit run -o shader -t '.*arb_shader_storage_buffer_object.*' results/shader > [9/9] pass: 9 / > > Signed-off-by: Hans de Goede <hdegoede at redhat.com> > --- > Changes in v2: > -New patch in v2 of patch-...

BTW, you may be interested in https://github.com/imirkin/mesa/commits/atomic3 which has working ARB_shader_atomic_counters and ARB_shader_storage_buffer_object support (while ripping out things like TGSI_FILE_RESOURCE). Still working on proper memory qualifier support, and obviously need to do some cleanup before upstreaming. Should be getting into a pushable state probably early January. Cheers, -ilia On Wed, Dec 16, 2015 at 12:24 PM, Ilia Mirkin &l...

I believe that your problem is this: /*01a0*/ LD R8, [R8]; /* 0x8000000000821c85 */ That needs to be LD.E (and your ST's need to be ST.E). You're using a 32-bit gmem address, but you need to be using a 64-bit one. I believe the 32-bit ones work on fermi, but afaik not on Kepler. Cheers, -ilia On Wed, Dec 16, 2015 at 12:06 PM, Hans de Goede

...Rename shader_glsl_ld_buffer() to shader_glsl_ld_raw_structured(). wined3d: Add support for atomic operations on thread group shared memory. wined3d: Add support for store_{raw, structured} on thread group shared memory. wined3d: Implement SM5 sync instruction. wined3d: Add ARB_shader_storage_buffer_object extension. d3d11/tests: Add test for thread group shared memory. wined3d: Don't leak texture in wined3d_unordered_access_view_destroy_object(). wined3d: Add support for atomic min/max operations on thread group shared memory. wined3d: Add FIXME() for unhandled UAV flags....

This approach leads to the emitters needing to know about both global and buffer, even though at that point, they are identical. I was thinking that in the lowering logic, buffer would just get rewritten as global (with the offset added), thus not needing any change to the emitters. What do you think about such an approach? On Mar 16, 2016 2:24 AM, "Hans de Goede" <hdegoede at