mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-01-24 10:54:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

* NEWS: Document that AC_C_RESTRICT checks 'restrict' last.

Browse Source 
* doc/autoconf.texi (C Compiler): Likewise.

2007-05-14  Noah Misch  <noah@cs.caltech.edu>

* lib/autoconf/c.m4 (AC_C_RESTRICT): Check `restrict' last.

* doc/autoconf.texi (Caching Results): The CACHE-ID variable
This commit is contained in:
Paul Eggert 2007-05-14 16:54:55 +00:00
parent 8c07b48727
commit d15e584f46
4 changed files with 25 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
ChangeLog
View File

@ -1,9 +1,18 @@
2007-05-14 Paul Eggert <eggert@cs.ucla.edu>
* NEWS: Document that AC_C_RESTRICT checks 'restrict' last.
* doc/autoconf.texi (C Compiler): Likewise.
2007-05-14 Noah Misch <noah@cs.caltech.edu>
* lib/autoconf/c.m4 (AC_C_RESTRICT): Check `restrict' last.
2007-05-09 Stepan Kasal <kasal@ucw.cz>
* doc/autoconf.texi: Direntry for "autoconf Invocation"
renamed to "autoconf-invocation"
* doc/autoconf.texi (Caching Results): The CACHE-ID variable
* doc/autoconf.texi (Caching Results): The CACHE-ID variable
in the examples should not use the internal "ac_" prefix.
2007-05-05 Noah Misch <noah@cs.caltech.edu>

4
NEWS
View File

@ -2,6 +2,10 @@
** AC_C_BIGENDIAN now supports universal binaries a la Mac OS X.
** AC_C_RESTRICT now prefers to #define 'restrict' to a variant spelling
like '__restrict' if the variant spelling is available, as this is
more likely to work when mixing C and C++ code.
** AC_CHECK_ALIGNOF's type argument T is now documented better: it must
be a string of tokens such that "T y;" is a valid member declaration
in a struct.

10
doc/autoconf.texi
View File

@ -6544,10 +6544,12 @@ New programs need not use this macro.
@defmac AC_C_RESTRICT
@acindex{C_RESTRICT}
@cvindex restrict
If the C compiler recognizes the @code{restrict} keyword, don't do anything.
If it recognizes only a variant spelling (@code{__restrict},
@code{__restrict__}, or @code{_Restrict}), then define
@code{restrict} to that.
If the C compiler recognizes a variant spelling for the @code{restrict}
keyword (@code{__restrict}, @code{__restrict__}, or @code{_Restrict}),
then define @code{restrict} to that; this is more likely to do the right
thing with compilers that support language variants where plain
@code{restrict} is not a keyword. Otherwise, if the C compiler
recognizes the @code{restrict} keyword, don't do anything.
Otherwise, define @code{restrict} to be empty.
Thus, programs may simply use @code{restrict} as if every C compiler
supported it; for those that do not, the makefile

9
lib/autoconf/c.m4
View File

@ -1647,9 +1647,10 @@ fi
# http://autoconf-archive.cryp.to/acx_restrict.html
#
# Determine whether the C/C++ compiler supports the "restrict" keyword
# introduced in ANSI C99, or an equivalent. Do nothing if the compiler
# accepts it. Otherwise, if the compiler supports an equivalent,
# define "restrict" to be that. Here are some variants:
# introduced in ANSI C99, or an equivalent. Define "restrict" to the alternate
# spelling, if any; these are more likely to work in both C and C++ compilers of
# the same family, and in the presence of varying compiler options. If only
# plain "restrict" works, do nothing. Here are some variants:
# - GCC supports both __restrict and __restrict__
# - older DEC Alpha C compilers support only __restrict
# - _Restrict is the only spelling accepted by Sun WorkShop 6 update 2 C
@ -1660,7 +1661,7 @@ AC_DEFUN([AC_C_RESTRICT],
[ac_cv_c_restrict=no
# Try the official restrict keyword, then gcc's __restrict, and
# the less common variants.
for ac_kw in restrict __restrict __restrict__ _Restrict; do
for ac_kw in __restrict __restrict__ _Restrict restrict; do
AC_COMPILE_IFELSE([AC_LANG_PROGRAM(
[[typedef int * int_ptr;
int foo (int_ptr $ac_kw ip) {