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

gccgo: does not understand CUNEIFORM SIGN DUG TIMES MI #12322

Closed
dvyukov opened this issue Aug 25, 2015 · 6 comments
Closed

gccgo: does not understand CUNEIFORM SIGN DUG TIMES MI #12322

dvyukov opened this issue Aug 25, 2015 · 6 comments
Milestone

Comments

@dvyukov
Copy link
Member

dvyukov commented Aug 25, 2015

gccgo rejects to compile the following program (in hex):

00000000  70 61 63 6b 61 67 65 20  61 0a 76 61 72 20 f0 92  |package a.var ..|
00000010  92 a4 20 3d 20 30 0a                              |.. = 0.|
00000017
/tmp/test.go:2:5: error: invalid character 0x124a4 in input file
 var 𒒤 = 0

That 0x124a4 seems to be a letter:
http://www.fileformat.info/info/unicode/char/124a4/index.htm

gofrontend is on commit 81810917af7ba19e1f9f8efc8b1989f7d6419d30

@dvyukov
Copy link
Member Author

dvyukov commented Aug 25, 2015

@ianlancetaylor

@dvyukov
Copy link
Member Author

dvyukov commented Aug 25, 2015

The same for ANATOLIAN HIEROGLYPH A137
0x144a4
http://www.fileformat.info/info/unicode/char/144a4/index.htm

@paranoiacblack paranoiacblack added this to the Gccgo milestone Aug 25, 2015
@paranoiacblack
Copy link
Contributor

This is just gccgo's unicode letter table being out of sync with the one in the unicode package.

@dvyukov
Copy link
Member Author

dvyukov commented Aug 28, 2015

What does it mean? Do I need to do some additional steps when integrating gofrontend into gcc?

@gopherbot
Copy link
Contributor

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

@paranoiacblack
Copy link
Contributor

Sorry, I sent out a CL to synchronize them; I expected the gopher bot to reply to this issue faster. But it would be nice to report any other valid unicode characters that are not accepted by gccgo in this issue. They should all be resolvable by updating the unicode table.

mydongistiny pushed a commit to mydongistiny/GCC_SaberMod that referenced this issue Oct 5, 2015
    
    Fixes golang/go#12322.
    
    Reviewed-on: https://go-review.googlesource.com/13985


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@228497 138bc75d-0d04-0410-961f-82ee72b054a4
@golang golang locked and limited conversation to collaborators Oct 4, 2016
asiekierka pushed a commit to WonderfulToolchain/gcc-ia16 that referenced this issue May 16, 2022
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

3 participants