On Fri, Jan 23, 2015 at 1:07 PM, Jason Ekstrand wrote:
>
>
> On Thu, Jan 22, 2015 at 8:32 PM, Connor Abbott wrote:
>>
>> Before, we used a system where a file, nir_opcodes.h, defined some macros
>> that
>> were included to generate the enum values and the nir_op_infos structure.
>> This
>> worked
On Thu, Jan 22, 2015 at 8:32 PM, Connor Abbott wrote:
> Before, we used a system where a file, nir_opcodes.h, defined some macros
> that
> were included to generate the enum values and the nir_op_infos structure.
> This
> worked pretty well, but for development the error messages were never very
Before, we used a system where a file, nir_opcodes.h, defined some macros that
were included to generate the enum values and the nir_op_infos structure. This
worked pretty well, but for development the error messages were never very
useful, Python tools couldn't understand the opcode list, and it w
