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

cmd/compile: treecopy Name #11361

Closed
dvyukov opened this issue Jun 23, 2015 · 2 comments
Closed

cmd/compile: treecopy Name #11361

dvyukov opened this issue Jun 23, 2015 · 2 comments
Milestone

Comments

@dvyukov
Copy link
Member

dvyukov commented Jun 23, 2015

Gc crashes on the following program:

package a
import "fmt"
const n = fmt
treecopy [0xc820209d40]
.   PACK l(2) a.fmt
tmp.go:3: internal compiler error: treecopy Name

This is a regression from Go1.4, it produced a sensible error message.

go version devel +514014c Thu Jun 18 15:54:35 2015 +0200 linux/amd64

@ianlancetaylor ianlancetaylor added this to the Go1.6 milestone Jul 11, 2015
@rsc rsc modified the milestones: Unplanned, Go1.6 Dec 5, 2015
@ramoas
Copy link

ramoas commented Jan 26, 2016

I also ran into this tonight in GO 1.5.1. Before finally finding this open issue, I took the time to upgrade to 1.5.3 and also tried 1.6 Beta 2. The fact that it still fails in all those versions is no surprise now given the "Unplanned, Go1.6" milestone target.

FWIW, in my case, I was using "crypto/x509," and I was trying to set my constant to x509.RSA (one of the three defined PublicKeyAlgorithms). Obviously, it was a silly mistake to leave off the ".RSA", but with that esoteric compiler error, it took me a few minutes to track down the problem, especially since I had made several other changes in my source files since my last successful compile.

Yes, once understood, the user error is easily correctable, but given this is apparently a regression from 1.4, please consider fixing for a 1.6 minor release or 1.7.

@gopherbot
Copy link

CL https://golang.org/cl/21936 mentions this issue.

@golang golang locked and limited conversation to collaborators Apr 13, 2017
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

6 participants