search for: _block_s

...o, 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 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 (using the first two words in the block as > the next and previous pointers). > &...

...M (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 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 (using the first two words in the block as the next and previous pointers). In the prologue, a fu...

..., 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 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 (using the first two words in the block as > the next and previous pointers). >...

...emented 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 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 (using the first two words in the block as >> the next and previous p...

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 (using the first two words in the block as > the next and previous pointers). W...