Displaying 5 results from an estimated 5 matches for "movimmz_i64".
2016 Jan 13
2
Expanding a PseudoOp and accessing the DAG
...I'm a bit worried that expansion happens too late (after
things should already be MI's, it seems). So things like patterns that try
to match on that XSTGMVINI would have already been matched.
[as an aside, we've got patterns like:
def : Pat<(XSTGMVINI tglobaladdr:$off),
(MOVIMMZ_I64 tglobaladdr:$off)>;
]
So, first off, if I wanted to expand that DAG for the RelAddr Node, and I
want something like (the first BuildMI below is pseudo code as I'm not sure
how to accomplish it):
case XSTG::RelAddr:
BuildMI(MBB, MI, DL, MI->getOperand(1).DAG...) ???
BuildMI(MBB...
2016 Jan 15
2
Expanding a PseudoOp and accessing the DAG
...eded to change it to:
>
> def: Pat<(load (XSTGADDR_NORMAL tglobaladdr:$addr)),
> (LOADI64_RI tglobaladdr:$addr, 0)>;
> // Match load from a relocatable address to a load with GRP:
> def: Pat<(load (XSTGADDR_USE_GRP tglobaladdr:$addr)),
> (LOADI64_RI (MOVIMMZ_I64 tglobaladdr:$addr), GRP)>;
Right.
> ...at least that gets through TableGen.
Excellent.
-Krzysztof
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
2016 Jan 15
2
Expanding a PseudoOp and accessing the DAG
On 1/15/2016 2:57 PM, Phil Tomson wrote:
>
>
> I see the following in my SelectCode (in XSTGGenDGISel.inc):
>
>
> /*2235*/ OPC_SwitchOpcode /*2 cases */, 27,
> TARGET_VAL(XSTGISD::ADDR_NORMAL),// ->2266
> /*2239*/ OPC_RecordChild0, // #1 = $addr
> /*2240*/ OPC_MoveChild, 0,
> /*2242*/ OPC_CheckOpcode,
2016 Jan 15
2
Expanding a PseudoOp and accessing the DAG
On Thu, Jan 14, 2016 at 6:05 AM, Krzysztof Parzyszek <
kparzysz at codeaurora.org> wrote:
> On 1/13/2016 4:47 PM, Phil Tomson wrote:
>
>>
>> First off, I got this idea from the LLVM Cookbook chapter 8: Writing an
>> LLVM Backend: Lowering to multiple instructions. (now I'm having my
>> doubts as to whether this is the right approach)
>>
>
>
2016 Jan 13
2
Expanding a PseudoOp and accessing the DAG
...allocation. In
> other words, quite late in the entire optimization sequence. Most of the
> actual optimization work is pretty much done at this point.
>
>
> [as an aside, we've got patterns like:
>>
>> def : Pat<(XSTGMVINI tglobaladdr:$off),
>> (MOVIMMZ_I64 tglobaladdr:$off)>;
>>
>> ]
>>
>
> I'm not sure if the input will match if you have tglobaladdr in it. The
> 't' means "target", and in this context it means that the argument has
> already been handled by the target and is in a form that does...