-
Notifications
You must be signed in to change notification settings - Fork 18k
x/net: please implement recvmsg and sendmsg under gccgo #52512
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 @ianlancetaylor |
It seems that various of system calls were not implemented. Same and some similar errors can be reproduced using the most recent gccgo (12.1 release). When trying to build Caddy with gccgo, the mentioned error could be reproduced:
For your information, go and gccgo versions are:
Thanks for your effort in investigating into this problem. |
I can't recreate the problems with golang.org/x/sys/unix. The problems with golang.org/x/net will require some updates to that package. It is using |
I wrote proposal #52885 as a step toward cleaning this up. |
Hi @ianlancetaylor, |
It should now be possible to rewrite the code in x/net to call |
I am working on a project where we port a larger GO application to a different platform and use gccgo for that purpose. For now, I stubbed the calls as the functionality might actually not needed. If I run into troubles, I will look into this! Thanks for the info! |
Change https://go.dev/cl/419175 mentions this issue: |
@ianlancetaylor Thanks a lot, that's appreciated. |
Update x/sys to permit calling RecvmsgBuffers and SendmsgBuffers. The zos changes are wholly untested. Fixes golang/go#52512 Change-Id: I8fae9f4db2e0b83c99a7c0f3cadc83b5868683e6 Reviewed-on: https://go-review.googlesource.com/c/net/+/419175 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Ian Lance Taylor <iant@google.com> Reviewed-by: Tobias Klauser <tobias.klauser@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes (gccgo 12-20220319-1, as shipped by Debian).
What operating system and processor architecture are you using (
go env
)?go env
What did you do?
What did you expect to see?
Build success.
What did you see instead?
The text was updated successfully, but these errors were encountered: