Skip to content
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

GOARM=5 binaries fail with GOMAXPROCS>1 or multicore #1494

Closed
rsc opened this issue Feb 10, 2011 · 1 comment
Closed

GOARM=5 binaries fail with GOMAXPROCS>1 or multicore #1494

rsc opened this issue Feb 10, 2011 · 1 comment

Comments

@rsc
Copy link
Contributor

rsc commented Feb 10, 2011

record runtime.GOARM during build, just as we record runtime.GOOS and runtime.GOARCH.

then on Linux use sched_setaffinity to force use of just one core if we end up with a
GOARM=5-built binary on a multiprocessor arm system.

GOARM=5 means no actual atomic operations, so use on a true multi-core system will fail.
@rsc
Copy link
Contributor Author

rsc commented Feb 25, 2011

Comment 2:

This issue was closed by revision 9ad9742.

Status changed to Fixed.

@rsc rsc added fixed labels Feb 25, 2011
@rsc rsc self-assigned this Feb 25, 2011
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants