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
gccgo: audit gccgo syscall package against gc syscall package #1790
Labels
Comments
Labels changed: added gccgo. Owner changed to @ianlancetaylor. |
Owner changed to builder@golang.org. |
Ian send me the generated 32- and 64-bit sysinfo.go and libcalls.go from the gccgo build, I put them into place renamed, added +build irix to socket_irix.go, and hacked up cmd/api a bit. Resulting diff for linux-amd64 attached. Attachments:
|
If others want to run this, Hacked up cmd/api is http://golang.org/cl/5776044 Generated files from Ian (and renamed) that you have to add to gccgo/libgo/go/syscall are attached. Then I run: $ pwd /home/bradfitz/hack/gccgo/libgo/go/syscall $ go tool api --dirs . | grep "^pkg syscall" > gccgo.txt Attachments:
|
I tried to compile most of the 6g tree with gccgo. It picked up the following, some of which are in the diff: exp/inotify turns up quite a few missing syscall bits. src/pkg/os/stat_linux.go:22:29: error: reference to undefined field or method ‘Mtim’ src/pkg/os/stat_linux.go:60:50: error: reference to undefined field or method ‘Atim’ and something quite strange: reflect/type.go:947:66: error: incompatible types in binary expression reflect/type.go:1009:69: error: incompatible types in binary expression Also, gccgo can't compile the builtin package. Maybe that's intentional. |
This was not fully fixed for the gcc 4.7.0 release. The full fix will have to be in 4.7.1. Labels changed: added priority-later, removed priority-go1. Owner changed to @ianlancetaylor. |
I see there's been some activity: http://code.google.com/p/gofrontend/source/detail?r=5016046ebbfea59cc34d1f7b3518440032f596aa It would be nice to get syscall.Mount fixed. |
On mainline I've gotten the changes down to the attached. At this point I'm inclined to close this bug report, unless anybody sees any specific items that need to be addressed. Attachments:
|
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: