Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: ejolson at unr dot edu
Target Milestone: ---
Created attachment 35648
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35648action=edit
Test code to illustrate bug. Must be run on at least
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66326
--- Comment #1 from Eric ejolson at unr dot edu ---
The compilers gcc-5.1 and cilkplus-4_8-branch were bootstrapped using the
Debian 4.7.2-5 gcc compiler on Debian Wheezy. Compiling and running the test
program yields the following output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66326
--- Comment #2 from Eric ejolson at unr dot edu ---
Additional information and discussion about this bug may be found on the Intel
Cilk Plus developer forum at
https://software.intel.com/en-us/forums/topic/558825
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 #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
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 #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 #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 #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
-finput
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 \
-finput-charset
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
Assignee: unassigned at gcc dot gnu.org
Reporter: ejolson at unr dot edu
Target Milestone: ---
Created attachment 36187
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36187action=edit
One line patch to add C99 UTF-8 support in identifiers to gcc
In response to FAQ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66326
--- Comment #3 from Eric ejolson at unr dot edu ---
GCC version 5.2 has come around and the bug is still here.
In particular, compiling for 32-bit Intel or using -mfpmath=387 in 64-bit leads
to immediate floating point exceptions. The fix
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.
Assignee: unassigned at gcc dot gnu.org
Reporter: ejolson at unr dot edu
Target Milestone: ---
Created attachment 41979
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41979=edit
Graph showing performance regression...
Code for gcc version 7.1 using Cilkplus paral
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81828
--- Comment #2 from Eric ---
(In reply to Andrew Pinski from comment #1)
> Note Cilk+ have been deprecated:
> https://gcc.gnu.org/gcc-7/changes.html
As 48-core ARM chips have just been announced by Qualcomm, now seems like the
wrong time to be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81828
--- Comment #3 from Eric ---
(In reply to Andrew Pinski from comment #1)
> Note Cilk+ have been deprecated:
> https://gcc.gnu.org/gcc-7/changes.html
As 48-core ARM chips have just been announced by Qualcomm, now seems like the
wrong time to be
18 matches
Mail list logo