Displaying 2 results from an estimated 2 matches for "__generic_morestack".
2011 Aug 11
2
[LLVMdev] Segmented Stacks: Breaking libgcc compatibility
...es coroutines
less interesting, since the whole point was to use multiple, cheap
stacks from a single 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
"conte...
2011 Aug 12
0
[LLVMdev] Segmented Stacks: Breaking libgcc compatibility
...esting, since the whole point was to use multiple, cheap
> stacks from a single 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...