search for: set_new_block_fp

...he function, the value at %rbp will also have to be copied to the new block, and %rbp will have to be changed to point to this new location (so that the FP relative indexing works). %rbp will then be set to its "correct" value by the epilogue itself. We'll probably need a new routine (set_new_block_fp) for this situation. **** Stack space for setup_new_block setup_new_block and setup_new_block_fp will be written to use the minimum amount of stack space possible, and that stack space will have to be factored into the check in the function prologue (so every function prologue checks for the...

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

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