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

Jump to bottom

cmd/go: compiler stdout/stderr should be cached #22587

Closed
rsc opened this issue Nov 5, 2017 · 1 comment
Closed

cmd/go: compiler stdout/stderr should be cached #22587

rsc opened this issue Nov 5, 2017 · 1 comment
Labels
FrozenDueToAge
Milestone
Go1.10

Comments

@rsc
Copy link
Contributor

rsc commented Nov 5, 2017

We cache the .a written by the compiler but not its output. This means that if you run -gcflags=-m twice, you only get to see the diagnostics once. We should fix that.
@rsc rsc added this to the Go1.10 milestone Nov 5, 2017
@rsc rsc mentioned this issue Nov 9, 2017
Closed
@gopherbot
Copy link

Change https://golang.org/cl/77110 mentions this issue: cmd/go: cache and replay command output during build

@rsc rsc mentioned this issue May 25, 2018
Closed
@golang golang locked and limited conversation to collaborators Nov 13, 2018
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.10
Development

No branches or pull requests
2 participants
@rsc @gopherbot