[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Neil Booth changed: What|Removed |Added CC||neilb at protonmail dot ch --- Comment #38

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Eric Gallager changed: What|Removed |Added CC||branning at gmail dot com,

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #36 from Manuel López-Ibáñez --- If the patch is in, it should be ok. Or ask in gcc-patches for someone to commit on your behalf. Gerald is very helpful. Just make sure the subject of the email is very clear. On Fri, 1 May 2020, 16:1

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #35 from Lewis Hyatt --- (In reply to Lewis Hyatt from comment #34) > (In reply to Eric Gallager from comment #33) > > This is a big enough feature that it should probably get an entry in > > gcc-10/changes.html > > I emailed a sugge

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #34 from Lewis Hyatt --- (In reply to Eric Gallager from comment #33) > This is a big enough feature that it should probably get an entry in > gcc-10/changes.html I emailed a suggested patch to that effect here: https://gcc.gnu.org/m

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Joseph S. Myers changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #31 from Joseph S. Myers --- Author: jsm28 Date: Thu Sep 19 19:56:11 2019 New Revision: 275979 URL: https://gcc.gnu.org/viewcvs?rev=275979&root=gcc&view=rev Log: Support extended characters in C/C++ identifiers (PR c/67224) libcpp/C

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #30 from joseph at codesourcery dot com --- https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future is the form to complete and send to ass...@gnu.org (to do an assignment covering past and future chan

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #29 from Lewis Hyatt --- (In reply to jos...@codesourcery.com from comment #28) > Thanks for working on this! I encourage sending this to gcc-patches once > a few fixes have been made and you've done the legal paperwork, see >

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #28 from joseph at codesourcery dot com --- On Mon, 22 Jul 2019, lhyatt at gmail dot com wrote: > I am interested in helping out with this if there is still interest to support > this feature. (Full disclosure, I don't have any exper

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #27 from Lewis Hyatt --- Created attachment 46620 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46620&action=edit second attempt at posting the patch Sorry, the previous patch I sent doesn't seem to show correctly in Bugzilla.

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Lewis Hyatt changed: What|Removed |Added CC||lhyatt at gmail dot com --- Comment #26 fr

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #25 from spoa at eircom dot net --- Many thanks Manu. The to_UCN.sh script works well. The only trouble was that my include file also contain unusual characters with diacritic marks and the script changes these file names to UCN als

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Manuel López-Ibáñez changed: What|Removed |Added Last reconfirmed|2015-08-17 00:00:00 |2017-10-30 --- Comment #24 from Ma

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 spoa at eircom dot net changed: What|Removed |Added CC||spoa at eircom dot net --- Comm

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Daniel Wolf changed: What|Removed |Added CC||dwolf at dannad dot de --- Comment #22 fro

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #21 from joseph at codesourcery dot com --- _cpp_interpret_identifier converts UCNs to UTF-8 which is the canonical internal form for identifiers - for UTF-8 in identifiers, you just need to pass in straight through unmodified there

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #20 from Eric --- I've been looking at the code in lex_identifier as well as what goes on in forms_identifier_p and so forth. As some point each identifier needs to be stored in the symbol table using ht_lookup_with_hash. Proper fun

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #19 from joseph at codesourcery dot com --- On Tue, 18 Aug 2015, ejolson at unr dot edu wrote: > which illustrates that g++ does not process trigraphs inside raw string > literals. Admittedly I'm looking at the draft standard, but I

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #18 from Eric --- Thanks Joseph for the clarification about the two different versions of iconv. I was admittedly confused about this until moments ago. Anyway, I just discovered that libiconv doesn't support conversions to and from

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #17 from joseph at codesourcery dot com --- On Tue, 18 Aug 2015, ejolson at unr dot edu wrote: > As iconv was installed on every GNU/Linux system I've tried, I'm not sure what > is wrong with using the C99 mode present in newer relea

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #16 from Eric --- With my second patch the command line must now include the options -finput-charset=UTF-8 -fextended-identifiers -fexec-charset=UTF-8 or otherwise C99 will also be used for the default execution character set.

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #15 from Eric --- Created attachment 36206 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36206&action=edit Improved UTF-8 identifier patch Improved patch to support UTF-8 identifiers. This version by default does no translati

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #14 from Eric --- While there may not be current demand for gcc to accept UTF-8 identifiers, the fact that clang and Visual Studio support this C99 feature means source code using Greek and accented characters in variable names is lik

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #13 from Manuel López-Ibáñez --- (In reply to Eric from comment #12) > I'm glad to know people like Joseph are working on UTF-8 in gcc. I think at the moment, neither Joseph nor anyone else is planning to work on this. There doesn't

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #12 from Eric --- I'm glad to know people like Joseph are working on UTF-8 in gcc. Last year I spent a week adding UTF-8 input support to pcc. At that time Microsoft Studio and clang already supported UTF-8 input files and I expecte

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #11 from joseph at codesourcery dot com --- Sorry, glibc iconv (not libiconv) doesn't handle "C99". So your patch would not work on any GNU host in normal configurations of GCC (libiconv is a completely separate package and is only

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #9 from Manuel López-Ibáñez --- (In reply to Eric from comment #7) > also contains example UTF-8 C99 input files which can be used to test the > compiler. The one-line patch submitted above has also been tested in the > sense that th

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #8 from Eric --- Created attachment 36196 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36196&action=edit Test program with UTF-8 identifiers... Compile this test program using gcc \ -finput-charset=UTF-8 -fextended-iden

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #7 from Eric --- Please look at the Raspberry Pi forum post linked in the original report for more information about testing this patch. As the text describes there, the command line options -finput-charset=UTF-8 -fextended-ide

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #6 from Eric --- >From the webpage (current as of Aug 17, 2015) http://www.gnu.org/software/libiconv/ under *Details* it is described that the library provides support for the following encodings: Full Unicode UTF-8

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #5 from joseph at codesourcery dot com --- There is no "C99" character set in glibc libiconv (after all, it's not a character set at all). Converting extended characters to UCNs like that would in any case be correct for C++ (provi

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #4 from Manuel López-Ibáñez --- I cannot say anything about the correctness of the patch, but I would expect such a patch to contain many testcases (at least similar to those that test for UCNs see https://gcc.gnu.org/ml/gcc-patches/2

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #3 from Andrew Pinski --- Have you tried -fextended-identifiers ?

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #2 from Andrew Pinski --- Related to bug 41374.

[Bug c/67224] UTF-8 support for identifier names in GCC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224 --- Comment #1 from Eric --- To check the installed version of iconv has C99 support type $ iconv --list | grep "C99" C99 $ which means that iconv is recent enough.