code review 101570044: undo CL 104200047 / 318b04f28372

undo CL 104200047 / 318b04f28372

Breaks windows and race detector.
TBR=rsc

««« original CL description
runtime: stack allocator, separate from mallocgc

In order to move malloc to Go, we need to have a
separate stack allocator.  If we run out of stack
during malloc, malloc will not be available
to allocate a new stack.

Stacks are the last remaining FlagNoGC objects in the
GC heap.  Once they are out, we can get rid of the
distinction between the allocated/blockboundary bits.
(This will be in a separate change.)

Fixes issue 7468
Fixes issue 7424

LGTM=rsc, dvyukov
R=golang-codereviews, dvyukov, khr, dave, rsc
CC=golang-codereviews
https://codereview.appspot.com/104200047
»»»

[khr, 2014-07-01 02:48:06]

Hello rsc (cc: golang-codereviews@googlegroups.com),

I'd like you to review this change to
https://khr%40golang.org@code.google.com/p/go/

[khr, 2014-07-01 02:48:16]

*** Submitted as https://code.google.com/p/go/source/detail?r=2c57aaea79c4 ***

undo CL 104200047 / 318b04f28372

Breaks windows and race detector.
TBR=rsc

««« original CL description
runtime: stack allocator, separate from mallocgc

In order to move malloc to Go, we need to have a
separate stack allocator.  If we run out of stack
during malloc, malloc will not be available
to allocate a new stack.

Stacks are the last remaining FlagNoGC objects in the
GC heap.  Once they are out, we can get rid of the
distinction between the allocated/blockboundary bits.
(This will be in a separate change.)

Fixes issue 7468
Fixes issue 7424

LGTM=rsc, dvyukov
R=golang-codereviews, dvyukov, khr, dave, rsc
CC=golang-codereviews
https://codereview.appspot.com/104200047
»»»

TBR=rsc
CC=golang-codereviews
https://codereview.appspot.com/101570044

[gobot, 2014-07-01 05:03:15]

This CL appears to have broken the nacl-amd64p32 builder.
See http://build.golang.org/log/96cf624ec82f6d9c3c72709db29d2686fb1cff4c