| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
because of Oz's suspicion that they may, in some mysterious way, contribute to
code-signing failures.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
being used as an operand to typeid'
|
|
|
|
|
|
|
|
|
|
MAINT-4952: Coverted VMM to coroutines
|
|
|
|
query part as well.
fix by Ansariel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hopefully we no longer need to brute-force remove any more macros with the
same name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Our first cut at tracking the "current" coroutine simply reset the pointer to
NULL every time we context-switched away. But that strategy doesn't handle the
case of coroutine A launching coroutine B.
Introduce LLCoros::CoroData to track, among other things, the previous value
of the current-coroutine pointer each time we switch into a coroutine. Restore
THAT value when we switch back out.
|
|
|
|
|
|
|
|
|
|
|
|
|
