This is to initially handleg immAllOnesV, which should match
G_BUILD_VECTOR or G_BUILD_VECTOR_TRUNC. In the future, it could be
used for other patterns cases that map to multiple G_* instructions,
such as G_ADD and G_PTR_ADD.
Details
Details
Diff Detail
Diff Detail
Event Timeline
llvm/utils/TableGen/GlobalISelEmitter.cpp | ||
---|---|---|
1674 | Typo "one several". |
Comment Actions
Could we have more than 2 possible choices for opcodes? Would it make sense to make this take an arbitrary number of alternatives?
Maybe something like
/// - InsnID - Instruction ID /// - NumChoices - Number of possible opcodes /// - Opcode1, Opcode2, Opcode3, ... OpcodeNumChoices - Possible opcodes, ordered by preference GIM_CheckOpcodeWithAlternatives
I can't think of anything off the top of my head, but it could be useful I suppose.
Comment Actions
I considered doing it this way, but I couldn't come up with a case where we would need more than 2. I'd rather use the simpler thing unless there's a concrete need
Comment Actions
Ok, that seems reasonable to me.
Do you think you can change the name from GIM_CheckOpcode2 to something more descriptive?
Typo "one several".