TDGen issue when the operand properties of the custom op do not match the ones in the (first) input operations

[Pekka Jääskeläinen]

When the custom op uses a commutative operation, say, ADD, the custom op should mark the same 'can swap' information to the operands going directly to the ADD. Otherwise, TDGen produces illegal patterns where an immediate is the first operand to a sub pattern.

Possible fix is to "inherit" the operand data automatically in this case, or at least produce an error message when this happens. Similar thing happens with the operand data types (custom operation operand datatype doesn't match the ones in the operations in the operation DAG) but it might not cause TDGen failures.

[Heikki Kultala (hkultala)]

failing test case for this would be nice to have.