-
Notifications
You must be signed in to change notification settings - Fork 18k
syscall, x/sys/unix: Select is not implemented on ppc64le #21946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/cc @laboger It looks like runtime:
|
The |
I'll have a fix for this shortly. |
Change https://golang.org/cl/65090 mentions this issue: |
Change https://golang.org/cl/65091 mentions this issue: |
Analog to the runtime package, Select should be using newselect instead of select. This change addresses this problem and regenerates zsyscall_linux_* for ppc64 and ppc64le. Updates golang/go#21946 Change-Id: I7ed5c2490ba2ce556f143f8e8377572ab345f7b8 Reviewed-on: https://go-review.googlesource.com/65091 Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Lynn Boger <laboger@linux.vnet.ibm.com>
Analog to the runtime package, syscall.Select should be using newselect instead of select. This change addresses this problem and regenerates zsyscall_linux_* for ppc64 and ppc64le. Updates #21946 Change-Id: I5dc3bf9e7f0b1172d6cce30ddf3bb1e3c95ec8e9 Reviewed-on: https://go-review.googlesource.com/65090 Run-TryBot: Lynn Boger <laboger@linux.vnet.ibm.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Lynn Boger <laboger@linux.vnet.ibm.com>
So I think the fix is merged and we can close this issue now |
What version of Go are you using (
go version
)?go version go1.9 linux/ppc64le
Does this issue reproduce with the latest release?
yes, with go1.9
What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
I hope it print
<nil>
which is the result on amd64.What did you see instead?
it prints
function not implemented
BTW, gccgo works fine.
The text was updated successfully, but these errors were encountered: