[Mesa-dev] [PATCH 14/25] i965: Update brw_instruction_name() with some recently added opcodes.
Francisco Jerez
currojerez at riseup.net
Mon Dec 2 11:39:22 PST 2013
---
src/mesa/drivers/dri/i965/brw_shader.cpp | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/brw_shader.cpp b/src/mesa/drivers/dri/i965/brw_shader.cpp
index 26300a6..dc6d35e 100644
--- a/src/mesa/drivers/dri/i965/brw_shader.cpp
+++ b/src/mesa/drivers/dri/i965/brw_shader.cpp
@@ -527,6 +527,26 @@ brw_instruction_name(enum opcode op)
case GS_OPCODE_SET_CHANNEL_MASKS:
return "set_channel_masks";
+ case SHADER_OPCODE_SHADER_TIME_ADD:
+ return "shader_time_add";
+
+ case SHADER_OPCODE_UNTYPED_ATOMIC:
+ return "untyped_atomic";
+ case SHADER_OPCODE_UNTYPED_SURFACE_READ:
+ return "untyped_surface_read";
+ case SHADER_OPCODE_UNTYPED_SURFACE_WRITE:
+ return "untyped_surface_write";
+
+ case SHADER_OPCODE_TYPED_ATOMIC:
+ return "typed_atomic";
+ case SHADER_OPCODE_TYPED_SURFACE_READ:
+ return "typed_surface_read";
+ case SHADER_OPCODE_TYPED_SURFACE_WRITE:
+ return "typed_surface_write";
+
+ case SHADER_OPCODE_MEMORY_FENCE:
+ return "memory_fence";
+
default:
/* Yes, this leaks. It's in debug code, it should never occur, and if
* it does, you should just add the case to the list above.
--
1.8.3.4
More information about the mesa-dev
mailing list