Displaying 3 results from an estimated 3 matches for "cleanup_new_block".
2011 Mar 28
2
[LLVMdev] RFC: GSoC Project
...ts using the fields in the va_list structure (and they point
back to the previous block, where the arguments actually are).
The return address placed on the new block is not the original
return address placed on the old stack by the callee, but is the address
of a another naked function (called cleanup_new_block) described below.
4. The stack pointer is set to (the address of the new block + 3 * word
size).
5. Control is returned to the prolgue, and execution continues
normally. We cannot use a usual ret here, so we'll have to use one of
the caller-saved registers to communicate the address of the ne...
2011 Mar 23
0
[LLVMdev] RFC: GSoC Project
On Wed, Mar 23, 2011 at 03:37:02PM +0530, Sanjoy Das wrote:
> I intend to start with the simplest possible approach - representing the
> stack as a doubly linked list of _block_s, the size of each _block_
> being a power of two. This can later be modified to improve performance
> and accommodate other factors. Blocks will be chained together into a
> doubly linked list structure
2011 Mar 23
5
[LLVMdev] RFC: GSoC Project
Hi All!
I will be applying to the LLVM project for this GSoC, and I wanted some
preliminary sanity check on my project idea.
I intend to implement split (segmented) stacks for LLVM (like we have in
Go, and as being implemented for GCC [1]). A lot of what follows is
lifted from [1]; I will progressively add more details as I get more
familiar with the LLVM codebase.
I intend to start with