From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Subject: Update c99status.html
Date: Sun, 19 Apr 2009 20:33:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0904192029020.23238@digraph.polyomino.org.uk> (raw)
I've applied this patch to update c99status.html regarding the status of
VLAs and stdint.h. Although there are some technical issues for VLAs
remaining for which I've filed the listed PRs, I think listing them as
"Done" is now fair as these corner cases are unlikely to be found in
ordinary code.
Index: c99status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/c99status.html,v
retrieving revision 1.50
diff -u -r1.50 c99status.html
--- c99status.html 29 Mar 2009 20:18:42 -0000 1.50
+++ c99status.html 19 Apr 2009 20:27:52 -0000
@@ -66,7 +66,7 @@
</tr>
<tr><td><em>variable-length arrays</em></td>
- <td></td><td></td><td>Broken</td>
+ <td></td><td>Done</td><td></td>
<td></td>
</tr>
@@ -342,12 +342,17 @@
requirements of the C99 standard.</li>
<li>There are some known bugs (<a
-href="http://gcc.gnu.org/PR19771">19771</a>, <a
href="http://gcc.gnu.org/PR39564">39564</a>, <a
href="http://gcc.gnu.org/PR39581">39581</a>, <a
href="http://gcc.gnu.org/PR39582">39582</a>) relating to corner cases
of variable length arrays (VLAs).</li>
+<li><code><stdint.h></code> is provided by GCC, or fixed where
+the system headers provide a nonconforming version, on some but not
+yet all systems. On systems where types in this header have been
+defined as <code>char</code>, GCC retains this definition although it
+is not permitted by C99.</li>
+
<li><code>const</code>-qualified compound literals could share storage
with each other and with string literals, but currently don't.</li>
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2009-04-19 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 20:33 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-23 9:46 Joseph S. Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0904192029020.23238@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).