This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C99 features
On Mon, 30 Jun 2003, Scott Robert Ladd wrote:
> The GCC C99 status page is a tad confusing. For example, "complex (and
> imaginary) support in <complex.h>" is "Broken", but it's not listed as a
> "library issue." Given that C99's complex.h is part of glibc, not gcc,
> I'm assuming this is an oversight in the status, or perhaps that the
The "in <complex.h>" is there only because that's what the text in C99
says: what's broken (or may be broken) is the complex types support in the
compiler and this entry is treated as describing the language support.
("may be" since one issue is lack of comparison of GCC's complex numbers
support with each relevant sentence in C99, and the other is a bug with
passing/returning complex values on 64-bit targets; I don't know whether
that bug is still present, but in any case that is just for some targets.)
> header can not be implemented base don the compiler's current state. The
> same problem exists with "extended integer types in <stdint.h>".
<stdint.h> isn't a library issue at all, since that header must be
provided by freestanding implementations - i.e., GCC should provide it.
Here the C99 entry was split up since <inttypes.h> is a library issue -
not required for freestanding implementations. (Providing <stdint.h> does
however need fixincludes work to play nicely with systems - such as
Solaris - with headers following an old C9X draft and providing only
<inttypes.h>, not <stdint.h>.)
The meaning of "Library Issue" is explained at the top of the page.
--
Joseph S. Myers
jsm28@cam.ac.uk