glsl: Just access the ir_expression_operation strings table directly
authorIan Romanick <ian.d.romanick@intel.com>
Thu, 16 Apr 2015 00:55:32 +0000 (17:55 -0700)
committerIan Romanick <ian.d.romanick@intel.com>
Tue, 30 Aug 2016 23:28:00 +0000 (16:28 -0700)
commitc6e8fd82ea118c66e69e4ad7967faec0715741aa
tree548a68d7abea31fc0f46ed2b093e249236d77a1b
parentfb44f69779ed7497768421ccd60e73cc707ffe69
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>
src/compiler/glsl/ir.cpp
src/compiler/glsl/ir.h
src/compiler/glsl/ir_expression_operation.py
src/compiler/glsl/ir_print_visitor.cpp
src/compiler/glsl/lower_mat_op_to_vec.cpp