-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/asm: type:xx
error in go1.20
#58244
Comments
type.xx
error in go1.20
It’s in the release notes: https://go.dev/doc/go1.20#linker. |
build error also |
type.xx
error in go1.20type.xx
error in go1.20
CC @golang/compiler |
I don't think we support reference type symbols in assembly code. And the name of type symbols is not guaranteed to be stable, and it can change at any time (as you noticed.) So this would not be expected to work. Thanks. |
@cherrymui This answer is unacceptable, it worked fine until 1.20. I think this may be caused by the linker change, but the compiler has not been modified. |
@cuonglm PTAL |
@timandy I'm not sure what else to do here. |
@timandy I'm sorry this change broke your code, but internal symbol names are always subject to change. We do not provide any guarantee for stability of assembler code. We do our best, of course, but we make no promises. These symbol names were changed for good reasons. |
@ianlancetaylor I'm not opposed to internal symbol modification, and golang is developing very well. The symbol name generated by the compiler changed, but the compiler did not recognize the new symbol when checking |
type.xx
error in go1.20type:xx
error in go1.20
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
MOVQ $type·int32(SB), AX
asm build error, but it works fine in go1.19
relocation target type.int32 not defined
The text was updated successfully, but these errors were encountered: