glsl: Just access the ir_expression_operation strings table directly

The operator_string functions gave us some protection against a
malformed table.  Now that the table is generated from the same data
that generates the enum, this is not a concern.  Just cut out the middle
man.

   text	   data	    bss	    dec	    hex	filename
7531892	 273992	  28584	7834468	 778b64	i965_dri-64bit-before.so
7531828	 273992	  28584	7834404	 778b24	i965_dri-64bit-after.so

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
This commit is contained in:
Ian Romanick
2015-04-15 17:55:32 -07:00
parent fb44f69779
commit c6e8fd82ea
5 changed files with 7 additions and 29 deletions

View File

@@ -255,7 +255,7 @@ void ir_print_visitor::visit(ir_expression *ir)
print_type(f, ir->type);
fprintf(f, " %s ", ir->operator_string());
fprintf(f, " %s ", ir_expression_operation_strings[ir->operation]);
for (unsigned i = 0; i < ir->get_num_operands(); i++) {
ir->operands[i]->accept(this);