https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
Eric Gallager changed:
What|Removed |Added
CC||branning at gmail dot com,
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,
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
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/bugzilla/show_bug.cgi?id=67224
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
Joseph S. Myers changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
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=gcc=rev
Log:
Support extended characters in C/C++ identifiers (PR c/67224)
libcpp/ChangeLog
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
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
>
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
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=edit
second attempt at posting the patch
Sorry, the previous patch I sent doesn't seem to show correctly in Bugzilla. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
Lewis Hyatt changed:
What|Removed |Added
CC||lhyatt at gmail dot com
--- Comment #26
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
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
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
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
Daniel Wolf changed:
What|Removed |Added
CC||dwolf at dannad dot de
--- Comment #22
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #20 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #21 from joseph at codesourcery dot com 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #13 from Manuel López-Ibáñez manu at gcc dot gnu.org ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #15 from Eric ejolson at unr dot edu ---
Created attachment 36206
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36206action=edit
Improved UTF-8 identifier patch
Improved patch to support UTF-8 identifiers. This version by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #14 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #17 from joseph at codesourcery dot com 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #16 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #19 from joseph at codesourcery dot com 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #18 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #12 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #6 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #7 from Eric ejolson at unr dot edu ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #8 from Eric ejolson at unr dot edu ---
Created attachment 36196
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36196action=edit
Test program with UTF-8 identifiers...
Compile this test program using
gcc \
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #9 from Manuel López-Ibáñez manu at gcc dot gnu.org ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
Manuel López-Ibáñez manu at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #11 from joseph at codesourcery dot com 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org ---
Have you tried -fextended-identifiers ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org ---
Related to bug 41374.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #5 from joseph at codesourcery dot com 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
--- Comment #4 from Manuel López-Ibáñez manu at gcc dot gnu.org ---
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/bugzilla/show_bug.cgi?id=67224
--- Comment #1 from Eric ejolson at unr dot edu ---
To check the installed version of iconv has C99 support type
$ iconv --list | grep C99
C99
$
which means that iconv is recent enough.
37 matches
Mail list logo
