- User Since
- Sep 5 2018, 10:24 PM (53 w, 5 d)
Wed, Sep 11
Tue, Sep 3
Thu, Aug 29
It can focus on whether the stack frame is created and not yet freed before the function call
for saving saved register or passing parameters or others.
Wed, Aug 28
If any arguments are passed by the stack, it is not allowed to do tail-call-opt.
Because the caller would allocate the stack for passing the arguments, and need to
free the stack after the call finished (the call must return back for free the stack).
Thu, Aug 22
Function with varargs passed by stack cannot be optimized to tail call.
If the varargs are all passed by registers, it can do tail call opt.
Aug 15 2019
Jun 16 2019
Hi, I am not really sure the means of TokenFactor. I refer the implement of other target.
From document, TokenFactor is used to represent the fact that the operand operators are independent of each other.
I am not sure why other target transform all stores into one single node by using TokenFactor.
Most of target, it uses sp+offset to store arguments into stack. So the order of store instruction doesn't matter.
In AVR, it uses push instruction to store arguments. Therefore. the order of store(push) instruction can't be changed.
Could you give me some suggestion? Thanks.
Jun 13 2019
Jun 9 2019
Jun 2 2019
May 27 2019
May 23 2019
Apr 14 2019
Apr 9 2019
Apr 8 2019
Add test case for large stack offset.
Mar 29 2019
Mar 28 2019
Dec 24 2018
Dec 4 2018
Remove unused fixme comment in test/CodeGen/X86/loop-search.ll.
Nov 29 2018
Remove unnecessary checking in test/CodeGen/WebAssembly/cfg-stackify.ll.
Nov 27 2018
Update test cases.