code review 55520043: syscall: use unsafe.Pointer in BSD kevent

syscall: use unsafe.Pointer in BSD kevent

Doesn't really matter for the most part, since the runtime-integrated
network poller uses its own kevent implementation, but for people using
the syscall directly, we should use an unsafe.Pointer for the precise GC
to retain the pointer arguments.

Also push down unsafe.Pointer a bit further in exec_linux.go, not
that there are any GC preemption points in the middle and sys
is still live anyway.

[bradfitz, 2014-01-22 06:12:25]

Hello golang-codereviews@googlegroups.com (cc: dvyukov@google.com,
iant@golang.org),

I'd like you to review this change to
https://go.googlecode.com/hg/

[dvyukov, 2014-01-22 18:29:20]

LGTM

[bradfitz, 2014-01-22 18:35:47]

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

syscall: use unsafe.Pointer in BSD kevent

Doesn't really matter for the most part, since the runtime-integrated
network poller uses its own kevent implementation, but for people using
the syscall directly, we should use an unsafe.Pointer for the precise GC
to retain the pointer arguments.

Also push down unsafe.Pointer a bit further in exec_linux.go, not
that there are any GC preemption points in the middle and sys
is still live anyway.

R=golang-codereviews, dvyukov
CC=golang-codereviews, iant
https://codereview.appspot.com/55520043