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: decide how to trigger gccgo #3157

Closed
rsc opened this issue Feb 29, 2012 · 2 comments
Closed

cmd/go: decide how to trigger gccgo #3157

rsc opened this issue Feb 29, 2012 · 2 comments
Labels
FrozenDueToAge
Milestone
Go1

Comments

@rsc
Copy link
Contributor

rsc commented Feb 29, 2012 

Right now we use $GC == "gccgo", which is
almost certainly wrong (GC is the wrong variable).
@rsc
Copy link
Contributor Author

rsc commented Mar 5, 2012

Comment 1:

Plan, as discussed on golang-dev:
1. add runtime.Compiler
2. rename build.Context.UseGccgo to build.Context.Compiler (Default = runtime.Compiler)
3. add a -compiler flag to go program
First step is CL 5720073.

@rsc
Copy link
Contributor Author

rsc commented Mar 6, 2012

Comment 2:

This issue was closed by revision 347cc98.

Status changed to Fixed.

@rsc rsc added fixed labels Mar 6, 2012
@rsc rsc self-assigned this Mar 6, 2012
@rsc rsc added this to the Go1 milestone Apr 10, 2015
@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.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1
Development

No branches or pull requests
2 participants
@rsc @gopherbot