search for: __generic_morestack_with_context

...le thread (and switch between them, at will). My current idea is to port segmented stack related routines to compiler-rt (or to a different "segmented-stacks" library altogether). That way, __generic_morestack (the function in libgcc that 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 __gen...

...them, at will). > > My current idea is to port segmented stack related routines to > compiler-rt (or to a different "segmented-stacks" library > altogether). That way, __generic_morestack (the function in libgcc > that 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 compile...