This is the mail archive of the
mailing list for the GCC project.
Re: C99 library issues
- From: Andreas Jaeger <aj at suse dot de>
- To: Paolo Carlini <pcarlini at unitus dot it>
- Cc: libc-alpha at sources dot redhat dot com, gcc at gcc dot gnu dot org
- Date: Mon, 19 Nov 2001 14:27:58 +0100
- Subject: Re: C99 library issues
- References: <3BF9058E.3E56B443@unitus.it>
- Reply-to: gcc-patches at gcc dot gnu dot org
Paolo Carlini <firstname.lastname@example.org> writes:
> perusing http://gcc.gnu.org/c99status.html I got the idea that there are some C99 features
> still missing from the current GLIBC library, right?
The note "Library issue" means that this is not a compiler issue. GCC
supports more systems than glibc based systems.
glibc 2.2.4 should implement all C99 issues, I'm not aware of anything
Perhaps a patch should be added to that page like the appended one. Ok
to commit it? Or should this get added to the section on "Library
issues" on top of the page?
RCS file: /cvs/gcc/wwwdocs/htdocs/c99status.html,v
retrieving revision 1.28
diff -u -p -r1.28 c99status.html
--- c99status.html 2001/11/12 22:52:54 1.28
+++ c99status.html 2001/11/19 13:27:27
@@ -374,6 +374,10 @@ implementations to do. The <code><st
<code><inttypes.h></code> entries have been separated, but are a
single entry in C99.</li>
+<li>The <a href="http://www.gnu.org/software/libc/libc.html">GNU C
+Library</a> implements all features that are marked as "Library Issue"
+since version 2.2.</li>
SuSE Labs email@example.com