From f3164c2ed96a119c73f16c4703bf5ad9feff1416 Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Fri, 30 Mar 2018 11:10:11 -0600 Subject: nir/spirv: s/uint32_t/SpvOp/ in various functions The MSVC compiler warns when the function parameter types don't exactly match with respect to enum vs. uint32_t. Use SpvOp everywhere. Alternately, uint32_t could be used everywhere. There doesn't seem to be an advantage to one over the other. Reviewed-by: Neil Roberts --- src/compiler/spirv/vtn_glsl450.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/compiler/spirv/vtn_glsl450.c') diff --git a/src/compiler/spirv/vtn_glsl450.c b/src/compiler/spirv/vtn_glsl450.c index eb0b90f7976..d208215ccb5 100644 --- a/src/compiler/spirv/vtn_glsl450.c +++ b/src/compiler/spirv/vtn_glsl450.c @@ -810,7 +810,7 @@ handle_glsl450_interpolation(struct vtn_builder *b, enum GLSLstd450 opcode, } bool -vtn_handle_glsl450_instruction(struct vtn_builder *b, uint32_t ext_opcode, +vtn_handle_glsl450_instruction(struct vtn_builder *b, SpvOp ext_opcode, const uint32_t *w, unsigned count) { switch ((enum GLSLstd450)ext_opcode) { -- cgit v1.2.3