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: scope of -gcflags #22833

Closed
aarzilli opened this issue Nov 21, 2017 · 2 comments
Closed

cmd/go: scope of -gcflags #22833

aarzilli opened this issue Nov 21, 2017 · 2 comments
Labels
FrozenDueToAge

Comments

@aarzilli
Copy link
Contributor

I see from the draft that:

The go build -asmflags, -gcflags, -gccgoflags, and -ldflags options now apply by default only to the packages listed directly on the command line

I missed when this changed happened but I liked it a lot more when -gcflags applied to all packages that contributed to the executable. I was hoping delve could drop the -a command line option with 1.10 and take advantage of caching but with this behavior I don't think we can.

cc @derekparker @heschik @hyangah
@huguesb
Copy link
Contributor

huguesb commented Nov 21, 2017

See #22527 for the discussion that lead to this change.

@aarzilli
Copy link
Contributor Author

Alright, I see that -gcflags=all=... exists, that's good enough for me.

@golang golang locked and limited conversation to collaborators Nov 21, 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
No milestone
Development

No branches or pull requests
3 participants
@aarzilli @huguesb @gopherbot