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.

Sign up for GitHub

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

Jump to bottom

cmd/go: go tool should not depend on archChar when using gccgo #7152

Closed
davecheney opened this issue Jan 20, 2014 · 2 comments
Closed

cmd/go: go tool should not depend on archChar when using gccgo #7152

davecheney opened this issue Jan 20, 2014 · 2 comments
Labels
FrozenDueToAge
Milestone
Go1.3

Comments

@davecheney
Copy link
Contributor 

What steps will reproduce the problem?

Currently cmd/go requires a valid archChar (from go/build.ArchChar()). 

Archchars are only used for the gc compiler, not gccgo.

Gccgo is available on architectures that gc does not currently support, for example
mips, arm64, but if cmd/go is compiled on those platforms it will refuse to run because
build.ArchChar does not return a valid result.

As archChars are only valid when compiling with gc, I propose that cmd/go be modified to
not resolve the archChar during startup.

Please use labels and text to provide additional information.
@davecheney
Copy link
Contributor Author

Comment 1:

https://golang.org/cl/54790044

Status changed to Started.

@davecheney
Copy link
Contributor Author

Comment 2:

This issue was closed by revision db37050.

Status changed to Fixed.

@rsc rsc added this to the Go1.3 milestone Apr 14, 2015
@rsc rsc removed the release-go1.3 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.3
Development

No branches or pull requests
3 participants
@davecheney @rsc @gopherbot