Displaying 2 results from an estimated 2 matches for "ldinst".
Did you mean:
oldinst
2012 Apr 19
0
[LLVMdev] Target Dependent Hexagon Packetizer patch
...The code above must match HexagonBaseInfo.h ***
>> }
>> @@ -47,17 +64,25 @@ class InstHexagon<dag outs, dag ins, string asmstr, list<dag> pattern,
>> // LD Instruction Class in V2/V3/V4.
>> // Definition of the instruction class NOT CHANGED.
>> class LDInst<dag outs, dag ins, string asmstr, list<dag> pattern>
>> - : InstHexagon<outs, ins, asmstr, pattern, "", LD> {
>> + : InstHexagon<outs, ins, asmstr, pattern, "", LD, TypeLD> {
>> + bits<5> rd;
>> + bits<5> rs;
&...
2012 Apr 26
2
[LLVMdev] MemRefs in a Load Instruction
...via this pattern. This causes the
loads to be volatile and "unpacketizable".
Is there no way to preserve or attach MemRefs to the LDriw instructions
generated by way of a pattern in the InstrInfo.td file ? FWIW, the LDriw
instruction is as show here.
let isPredicable = 1 in
def LDriw : LDInst<(outs IntRegs:$dst),
(ins MEMri:$addr), "$dst = memw($addr)",
[(set IntRegs:$dst, (i32 (load ADDRriS11_2:$addr)))]>;
TIA,
Pranav
Qualcomm Innovation Center, (QuIC) is a member of the Code Aurora Forum.