-
Notifications
You must be signed in to change notification settings - Fork 18k
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: crypto/elliptic build error under -linkshared mode [1.20 backport] #59236
Comments
The issue affects projects built with |
Change https://go.dev/cl/479355 mentions this issue: |
cc @heschi |
Even though this affects generics, the fix seems safe, since it only applies to linkshared. Approved. |
…methods in linkshared mode For G[T] that was seen and compiled in imported package, it is not added to typecheck.Target.Decls, prevent wasting compile time re-creating DUPOKS symbols. However, the linker do not support a type symbol referencing a method symbol across DSO boundary. That causes unreachable sym error when building under -linkshared mode. To fix it, always re-compile generic methods in linkshared mode. Fixes #59236 Change-Id: I894b417cfe8234ae1fe809cc975889345df22cef Reviewed-on: https://go-review.googlesource.com/c/go/+/477375 Run-TryBot: Cuong Manh Le <cuong.manhle.vn@gmail.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-on: https://go-review.googlesource.com/c/go/+/479355
FWIW, the compiler team's concerns with generics backports was largely specific to the Go 1.18 release. Especially since Go 1.20, I think we can treat generics issues the same as any other compiler/language issue. |
Closed by merging 94c02a3 to release-branch.go1.20. |
@cuonglm requested issue #58966 to be considered for backport to the next 1.20 minor release.
The text was updated successfully, but these errors were encountered: