search for: __generic_morestack_context

...t allocates space for a new stacklet) gets a cousin __generic_morestack_with_context, which take a pointer to a "context" holding the otherwise thread local variables use by libgcc's __generic_morestack. That way, every coroutine can have its own "context" which it passes to __generic_morestack_context. __generic_morestack in compiler-rt can then call __generic_morestack with a context which it holds in a TLS variable, to take care of the most common case. Does this sound sane? Thanks! -- Sanjoy Das http://playingwithpointers.com

...r a new stacklet) gets a cousin > __generic_morestack_with_context, which take a pointer to a "context" > holding the otherwise thread local variables use by libgcc's > __generic_morestack. That way, every coroutine can have its own > "context" which it passes to __generic_morestack_context. > > __generic_morestack in compiler-rt can then call __generic_morestack > with a context which it holds in a TLS variable, to take care of the > most common case. I think it is important to retain gcc compatibility, at least in the following sense: if someone only wants to make use o...