diff options
author | Marek Olšák <[email protected]> | 2016-03-10 13:20:36 +0100 |
---|---|---|
committer | Marek Olšák <[email protected]> | 2016-03-19 23:20:01 +0100 |
commit | fbe6e92899f90e7ee85420e88c807a1f2fd2be14 (patch) | |
tree | e26372e2b5ff06e17f5308fef405c1829126bcdd /src/gallium/auxiliary/tgsi/tgsi_strings.c | |
parent | 9184d9a0bbe8a8b88d676a20f95d66ceee9eaf21 (diff) |
gallium: add TGSI property NEXT_SHADER
Radeonsi needs to know which shader stage will execute after a shader
in order to make the best decision about which shader variant to compile
first.
This is only set for VS and TES, because we don't need it elsewhere.
VS has 3 variants:
- next shader is FS
- next shader is GS
- next shader is TCS
TES has 2 variants:
- next shader is FS
- next shader is GS
Currently, radeonsi always assumes the next shader is FS, which is suboptimal,
since st/mesa always knows which shader is next if the GLSL program is not
a "separate shader".
By default, ureg always sets "next shader is FS".
Reviewed-by: Nicolai Hähnle <[email protected]>
Diffstat (limited to 'src/gallium/auxiliary/tgsi/tgsi_strings.c')
-rw-r--r-- | src/gallium/auxiliary/tgsi/tgsi_strings.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/gallium/auxiliary/tgsi/tgsi_strings.c b/src/gallium/auxiliary/tgsi/tgsi_strings.c index 6bd1a2e14d2..ae779a8320a 100644 --- a/src/gallium/auxiliary/tgsi/tgsi_strings.c +++ b/src/gallium/auxiliary/tgsi/tgsi_strings.c @@ -145,6 +145,7 @@ const char *tgsi_property_names[TGSI_PROPERTY_COUNT] = "NUM_CLIPDIST_ENABLED", "NUM_CULLDIST_ENABLED", "FS_EARLY_DEPTH_STENCIL", + "NEXT_SHADER", }; const char *tgsi_return_type_names[TGSI_RETURN_TYPE_COUNT] = |