-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/compile: access slice is slow #29805
Comments
You seem to be implementing a slice on top of a slice. Every bounds check is going to be done twice. Your benchmark using |
I don't see a bug here, so I'm going to close this. If you want to discuss writing & profiling Go code, let's bring this to the mailing list or other forum. See https://golang.org/wiki/Questions. |
so, why only win7 is very slow, the some code, same hardware. is this not a bug? wtf |
There are many possible reasons. Windows 7 is almost 10 years old and spending time to investigate whether there is a problem on Windows 7 is not going to be a priority for the Go team. Even if there is a problem there is a good chance that it has something to do with details of the OS and that there is nothing we can do to fix it. As suggested above, I recommend that you investigate this in a forum. If you find a specific problem, we can reconsider. |
here is my codes.
On Windows 7 64bit, go version go1.11.4 windows/amd64. the VectorInt.Push is very slow, it costs about 12ns.
but on Win10 about 2ns, Linux about 2ns
The text was updated successfully, but these errors were encountered: