Fix for bug #4365.
…er aborting the former.
The problem was two folds. First, a parent task wasn't correctly waiting on the inner task continuations that were setup. Second, the way the Task parent field was re-used with a continuation collided with the parenting behavior of AttachedToParent (if the continuation was also created that way), the fix is to have two Task fields to differentiate between the two cases.
…voke3 OSX with -O2.
…ing async requests. Fixes #2473.
…tart date Thanks to Kirill for this patch. Bug #2223.
…lculations on win32.
…een called anymore.
…inor overflow. Fixes bxc #2349 and bxc #2091. * sgen-bridge.c: * sgen-gc.c: After we split bridge processing in two, one step with world stopped and another with world running, we introduced the following regression: A minor collection starts and find an young bridge object ready to be processed. Major heap overflows and a major GC is triggered. The object mentioned above will remain collectible and will be queued for processing again. Since we do the first step in finish_gray_stack, it will be done twice in the above scenario. This will cause an assertion due to duplicate entries in the hashtable. The solution is to split the step that is performed with world stopped into another two. One that happens during collections, that can be done multiple times per duty cycle and another one that is done only once before we restart the world. This split has the minor advantage of reducing duplicated work for the dfs1 step. Nothing big as this is one of the fastest steps.
…s and superclasses of generic instances. Fixes #2155