Displaying 2 results from an estimated 2 matches for "opc_emitmergeinputchains".
2016 Jul 29
2
Help with ISEL matching for an SDAG
...8,
ScalarLoads.Li8, ScalarLoads.Li8,
ScalarLoads.Li8, ScalarLoads.Li8)),
(v16i8 (VSPLTBs 7, (LXSIBZX xoaddr:$src)))>;
But it doesn't match it. The matching fails at an index that corresponds to
the following line:
OPC_EmitMergeInputChains, 16, 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
14, 15, 16,
I don't know what that line means. Can someone help?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/953fac0d/attachment.html>...
2014 Apr 26
2
[LLVMdev] How can I get rid of "OPFL_Chain" in myCPUGenInstrInfo.inc
...str
<0x0,
(outs Intregs:$dst) (ins Intregs:$op0,MEMi:$op1),
"",
[set IntRegs:$dest (adde IntRegs:$op0, (load ADDRi:$op1))]
>
very unlucky, this instruction failed.
in the generated match table, there was flag OPFL_Chain.
it caused a token factor node to be created in switch case
OPC_EmitMergeInputChains in SelectCodeCommon.
very bad, all uses of input chain was replaced with ADDErm Node.
so the created token factor node depends on the ADDErm node after the
replacement.
very bad the ADDCrm node depends on above token factor.
because of the glue, a cycle formed. ADDE-->ADDC-->TF-->A...