christopher.lamb at gmail.com
Wed Apr 18 11:25:52 PDT 2007
I noticed that the TableGen code emitter generator assumes that the
instruction fields are declared in the instruction format in the same
order that operands are defined. This seems like a bad dependence to
me, and that TableGen should match the name of field declared in the
instruction with the name of the operand in order to determine which
operand of the MI to use
See CodeEmitterGen.cpp:170 and neighborhood.
Unfortunately there are naming discrepancies between the instruction
format fields and the operand names in all existing code emitters
that use TableGen, which would require some significant renaming
Thoughts on binding operand names to instruction field names for the
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev