diff mbox

Update c99status.html for extended identifiers changes

Message ID alpine.DEB.2.10.1411062120420.17254@digraph.polyomino.org.uk
State New
Headers show

Commit Message

Joseph Myers Nov. 6, 2014, 9:31 p.m. UTC 
I've applied this patch to update c99status.html for the recent changes 
regarding extended identifiers.  The remaining known C99/C11 conformance 
issues (beyond ordinary bugs) are all floating-point issues (mostly but 
not entirely Annex F/G).

Comments

Marek Polacek Nov. 6, 2014, 9:38 p.m. UTC | #1 
On Thu, Nov 06, 2014 at 09:31:46PM +0000, Joseph Myers wrote:
> I've applied this patch to update c99status.html for the recent changes 
> regarding extended identifiers.  The remaining known C99/C11 conformance 
> issues (beyond ordinary bugs) are all floating-point issues (mostly but 
> not entirely Annex F/G).

Thanks.  I think we also should mention the extended identifiers
change in changes.html.

	Marek
Joseph Myers Nov. 6, 2014, 9:50 p.m. UTC | #2 
On Thu, 6 Nov 2014, Marek Polacek wrote:

> On Thu, Nov 06, 2014 at 09:31:46PM +0000, Joseph Myers wrote:
> > I've applied this patch to update c99status.html for the recent changes 
> > regarding extended identifiers.  The remaining known C99/C11 conformance 
> > issues (beyond ordinary bugs) are all floating-point issues (mostly but 
> > not entirely Annex F/G).
> 
> Thanks.  I think we also should mention the extended identifiers
> change in changes.html.

Note that extended identifiers are still only supported in the form using 
UCNs, not directly using the extended characters (other than $).  I don't 
think it would be hard to support extended characters in identifiers if 
desired (and it would certainly be friendlier for users wishing to use 
such characters in identifiers to be able to write them directly), but I 
don't plan to work on that for GCC 5 (and there are design questions to 
consider regarding e.g. how you handle random characters that aren't valid 
in identifiers).
diff mbox

Patch

Index: c99status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/c99status.html,v
retrieving revision 1.62
diff -u -r1.62 c99status.html
--- c99status.html	27 Oct 2013 15:41:51 -0000	1.62
+++ c99status.html	6 Nov 2014 21:18:36 -0000
@@ -8,9 +8,9 @@ 
 <h1>Status of C99 features in GCC</h1>
 
 <p>C99 is substantially completely supported as of GCC 4.5
-(with <code>-std=c99 -pedantic-errors</code> used), modulo bugs,
-extended identifiers (supported except for corner cases
-when <code>-fextended-identifiers</code> is used), and floating-point
+(with <code>-std=c99 -pedantic-errors</code> used;
+<code>-fextended-identifiers</code> also needed to enable extended
+identifiers before GCC 5), modulo bugs and floating-point
 issues (mainly but not entirely relating to optional C99 features from
 Annexes F and G).  The following table gives more details of the C99
 support in different GCC versions.</p>
@@ -30,7 +30,8 @@ 
 if additional compiler features could be useful in conjunction with
 it.  It is assumed that GCC is used with <code>-std=c99
 -pedantic-errors</code> (for versions 3.0 and later), as well
-as <code>-fextended-identifiers</code> in the case of that feature.
+as <code>-fextended-identifiers</code> in the case of that feature
+before GCC 5.
 Where library cooperation is required, it is assumed that a recent
 version of the GNU C Library is in use, and support with other C
 libraries may be less good.  Where the version listed is before GCC
@@ -138,8 +139,9 @@ 
 
 <tr><td><em>extended identifiers</em></td>
     <td>GCC 4.1</td>
-    <td>Requires <code>-fextended-identifiers</code> and some corner
-    cases may be broken.</td>
+    <td>Some corner cases were fixed in GCC 5;
+    <code>-fextended-identifiers</code> was needed to enable this
+    feature before that version.</td>
 </tr>
 
 <tr><td><em>hexadecimal floating-point constants and