r300: Disable fp16 and int16 in swtcl vertex shaders.
We already had them disabled for hwtcl, but in the swtcl case gallivm's
param query would return (nir) support even though nir-to-tgsi couldn't
handle it because TGSI doesn't do fp16/int16.
Fixes: 7d2ea9b0ed
("r300: Request NIR shaders from mesa/st and use NIR-to-TGSI.")
Reviewed-by: Matt Turner <mattst88@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14809>
This commit is contained in:
parent
965d58b058
commit
be78087655
|
@ -350,6 +350,15 @@ static int r300_get_shader_param(struct pipe_screen *pscreen,
|
|||
case PIPE_SHADER_CAP_INTEGERS:
|
||||
return 0;
|
||||
|
||||
/* Even if gallivm NIR can do this, we call nir_to_tgsi manually and
|
||||
* TGSI can't.
|
||||
*/
|
||||
case PIPE_SHADER_CAP_INT16:
|
||||
case PIPE_SHADER_CAP_FP16:
|
||||
case PIPE_SHADER_CAP_FP16_DERIVATIVES:
|
||||
case PIPE_SHADER_CAP_FP16_CONST_BUFFERS:
|
||||
return 0;
|
||||
|
||||
/* While draw could normally handle this for the VS, the NIR lowering
|
||||
* to regs can't handle our non-native-integers, so we have to lower to
|
||||
* if ladders.
|
||||
|
|
Loading…
Reference in New Issue