search for: setup_new_block_coroutine

...he first block in the chain of blocks to follow. The structure of the block will be similar to the structure of a regular stack block, except that it will also have space to store two registers - this_ip and this_sp. The prologue of a co-routine will jump to a function similar to setup_new_block (setup_new_block_coroutine) which will work like setup_new_block, except: 1. It will first check if saved_stack is NULL. If it is NULL, it will allocate a new block and save it to saved_stack. It if isn't, it'll simply restore saved_sp, saved_ip. 2. In case a new block was allocated, it will pretty much do what set...

...ocks to follow. > > The structure of the block will be similar to the structure of a regular > stack block, except that it will also have space to store two registers > - this_ip and this_sp. > > The prologue of a co-routine will jump to a function similar to > setup_new_block (setup_new_block_coroutine) which will work like > setup_new_block, except: > > 1. It will first check if saved_stack is NULL. If it is NULL, it will > allocate a new block and save it to saved_stack. It if isn't, it'll > simply restore saved_sp, saved_ip. > > 2. In case a new block was allocated...

...;> The structure of the block will be similar to the structure of a regular >> stack block, except that it will also have space to store two registers >> - this_ip and this_sp. >> >> The prologue of a co-routine will jump to a function similar to >> setup_new_block (setup_new_block_coroutine) which will work like >> setup_new_block, except: >> >> 1. It will first check if saved_stack is NULL. If it is NULL, it will >> allocate a new block and save it to saved_stack. It if isn't, it'll >> simply restore saved_sp, saved_ip. >> >> 2. In ca...

...of the block will be similar to the structure of a regular >>> stack block, except that it will also have space to store two registers >>> - this_ip and this_sp. >>> >>> The prologue of a co-routine will jump to a function similar to >>> setup_new_block (setup_new_block_coroutine) which will work like >>> setup_new_block, except: >>> >>> 1. It will first check if saved_stack is NULL. If it is NULL, it will >>> allocate a new block and save it to saved_stack. It if isn't, it'll >>> simply restore saved_sp, saved_ip. >&g...

On Sun, Apr 10, 2011 at 4:16 PM, Chris Lattner <clattner at apple.com> wrote: > > On Apr 10, 2011, at 2:45 PM, Talin wrote: > > I wonder - would something like this allow for multiple stacks for a single > thread? I'm thinking of something like continuations / fibers / green > threads, which would be very handy. > > > I haven't looked at the proposal, but

On Apr 10, 2011, at 2:45 PM, Talin wrote: > I wonder - would something like this allow for multiple stacks for a single thread? I'm thinking of something like continuations / fibers / green threads, which would be very handy. I haven't looked at the proposal, but yes, this would be very useful functionality for LLVM to provide. -Chris > > On Wed, Mar 23, 2011 at 3:07 AM,