code review 12424045: undo CL 12250043 / e911f94c4902

undo CL 12250043 / e911f94c4902

Break all 386 builders.

««« original CL description
runtime: use gcpc/gcsp during traceback of goroutines in syscalls
gcpc/gcsp are used by GC in similar situation.
gcpc/gcsp are also more stable than gp->sched,
because gp->sched is mutated by entersyscall/exitsyscall
in morestack and mcall. So it has higher chances of being inconsistent.
Also, rename gcpc/gcsp to syscallpc/syscallsp.

R=golang-dev, rsc
CC=golang-dev
https://codereview.appspot.com/12250043
»»»

[dvyukov, 2013-08-05 19:32:35]

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

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

[dvyukov, 2013-08-05 19:32:55]

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

Please take another look.

[dvyukov, 2013-08-05 19:33:58]

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

undo CL 12250043 / e911f94c4902

Break all 386 builders.

««« original CL description
runtime: use gcpc/gcsp during traceback of goroutines in syscalls
gcpc/gcsp are used by GC in similar situation.
gcpc/gcsp are also more stable than gp->sched,
because gp->sched is mutated by entersyscall/exitsyscall
in morestack and mcall. So it has higher chances of being inconsistent.
Also, rename gcpc/gcsp to syscallpc/syscallsp.

R=golang-dev, rsc
CC=golang-dev
https://codereview.appspot.com/12250043
»»»

R=rsc
CC=golang-dev
https://codereview.appspot.com/12424045

[rsc, 2013-08-05 19:49:51]

LGTM