Am 19.01.2016 um 18:26 schrieb Ilia Mirkin:
> This is designed to map the GLSL intrinsics. Should one have a desire
> to also support d3d11, one could figure out what the overlap is and
> rejigger the arguments so that both sets of desires are expressible. I
> glanced at SM5 sync before doing
I am actually wondering how well that would work for d3d11.
d3d11 just has AllMemoryBarrier, DeviceMemoryBarrier plus
GroupMemoryBarrier - and for each of them also a "WithGroupSync"
version. Hmm.
Roland
Am 19.01.2016 um 03:30 schrieb Ilia Mirkin:
> Signed-off-by: Ilia Mirkin
This is designed to map the GLSL intrinsics. Should one have a desire
to also support d3d11, one could figure out what the overlap is and
rejigger the arguments so that both sets of desires are expressible. I
glanced at SM5 sync before doing this, and TBH I couldn't really make
sense of it:
Signed-off-by: Ilia Mirkin
Reviewed-by: Marek Olšák (v1)
v1 -> v2: add defines for the various bits
---
src/gallium/auxiliary/tgsi/tgsi_info.c | 2 +-
src/gallium/docs/source/tgsi.rst | 17 +