]> Cypherpunks repositories - gostls13.git/commit
syscall: use unsafe.Pointer in BSD kevent
authorBrad Fitzpatrick <bradfitz@golang.org>
Wed, 22 Jan 2014 18:35:41 +0000 (10:35 -0800)
committerBrad Fitzpatrick <bradfitz@golang.org>
Wed, 22 Jan 2014 18:35:41 +0000 (10:35 -0800)
commitba8c92c1660bf86dfeedfc41ac39683c7e0d7607
treea335b567f79b5be3193b42f070789d7b51cbb9a4
parentb7b93a7154ea1b569019e9d993f21a52d8aeda14
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://golang.org/cl/55520043
14 files changed:
src/pkg/syscall/exec_linux.go
src/pkg/syscall/syscall_bsd.go
src/pkg/syscall/zsyscall_darwin_386.go
src/pkg/syscall/zsyscall_darwin_amd64.go
src/pkg/syscall/zsyscall_dragonfly_386.go
src/pkg/syscall/zsyscall_dragonfly_amd64.go
src/pkg/syscall/zsyscall_freebsd_386.go
src/pkg/syscall/zsyscall_freebsd_amd64.go
src/pkg/syscall/zsyscall_freebsd_arm.go
src/pkg/syscall/zsyscall_netbsd_386.go
src/pkg/syscall/zsyscall_netbsd_amd64.go
src/pkg/syscall/zsyscall_netbsd_arm.go
src/pkg/syscall/zsyscall_openbsd_386.go
src/pkg/syscall/zsyscall_openbsd_amd64.go