You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
gccgo tip
go version go1.10.3 gccgo (GCC) 9.0.0 20180920 (experimental) linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
linux/amd64
What did you do?
Unpack tar file tarfile.gz
in your $GOPATH, change dir to Äbar, then build.
What did you expect to see?
Clean build
What did you see instead?
$ tar xzvf - < tarfile.gz
./Äbar/
./Äbar/Äbar.go
./Äfoo/
./Äfoo/Äfoo.go
$ cd ./Äbar/
$ go build -compiler gccgo .
$ go build -compiler gccgo .
# Äbar
./Äbar.go:5:7: error: imported and not used: Äfoo
5 | "Äfoo"
| ^
./Äbar.go:9:45: error: reference to undefined name ‘Äfoo’
9 | fmt.Printf("Äfoo.Äbar(33) returns %v\n", Äfoo.Äbar(33))
| ^
$
This program builds cleanly with the regular Go compiler.
I need to spend more time in the debugger, but I think this is a parsing issue, since it is happening very early in the compilation. The call to Äfoo.Äbar is somehow not getting tracked as a reference to the Äfoo package, hence the incorrect error. More investigation needed.
The text was updated successfully, but these errors were encountered:
Also includes a small tweak to test/run.go to allow package names
with Unicode letters (as opposed to just ASCII chars).
Updates #27836
Change-Id: Idbf0bdea24174808cddcb69974dab820eb13e521
Reviewed-on: https://go-review.googlesource.com/138075
Reviewed-by: Cherry Zhang <[email protected]>
Fix a bug in the parser code that decides whether a given name should
be considered exported or not. The function Lex::is_exported_name
(which assumes that its input is a mangled name) was being called on
non-mangled (raw utf-8) names in various places. For the bug in
question this caused an imported package to be registered under the
wrong name. To fix the issue, rename 'Lex::is_exported_name' to
'Lex::is_exported_mangled_name', and add a new 'Lex::is_exported_name'
that works on utf-8 strings.
Fixesgolang/go#27836.
Reviewed-on: https://go-review.googlesource.com/137736
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@264690 138bc75d-0d04-0410-961f-82ee72b054a4
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?gccgo tip
go version go1.10.3 gccgo (GCC) 9.0.0 20180920 (experimental) linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?linux/amd64
What did you do?
Unpack tar file tarfile.gz
in your $GOPATH, change dir to Äbar, then build.
What did you expect to see?
Clean build
What did you see instead?
This program builds cleanly with the regular Go compiler.
I need to spend more time in the debugger, but I think this is a parsing issue, since it is happening very early in the compilation. The call to Äfoo.Äbar is somehow not getting tracked as a reference to the Äfoo package, hence the incorrect error. More investigation needed.
The text was updated successfully, but these errors were encountered: