* doc/autoconf.texi (C Compiler): Mention that AC_PROG_CC_C99 also

checks for unsigned long long int.

diff --git a/ChangeLog b/ChangeLog
index 29c6c0025ccc1acb7c6e81482185575049bcf038..d360068d3301ca27f88b9225044689a34c5987dc 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2007-03-23  Paul Eggert  <eggert@cs.ucla.edu>
+
+       * doc/autoconf.texi (C Compiler): Mention that AC_PROG_CC_C99 also
+       checks for unsigned long long int.
+
 2007-03-19  Paul Eggert  <eggert@cs.ucla.edu>
 
        * doc/autoconf.texi (Limitations of Usual Tools): Warn about other

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 817ab5c4c88da09477a8cfd8f32107ba6c23a803..6fa70364721130e77cc802996ef4fd509fca5e46 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -6438,8 +6438,9 @@ If the C compiler is not in C99 mode by default, try to add an
 option to output variable @code{CC} to make it so.  This macro tries
 various options that select C99 on some system or another.  It
 considers the compiler to be in C99 mode if it handles @code{_Bool},
-@code{//} comments, flexible array members, @code{inline}, @code{long
-long int}, mixed code and declarations, named initialization of structs,
+@code{//} comments, flexible array members, @code{inline}, signed and
+unsigned @code{long long int}, mixed code and declarations, named
+initialization of structs,
 @code{restrict}, @code{va_copy}, varargs macros, variable declarations
 in @code{for} loops, and variable length arrays.