Dwight Guth wrote:
We use GLIBC's header files, but we
do not define the __GNUC__ macro.
Ah, in that case there's a simple solution: your compiler should define
__GNUC__. That's what Clang does.
we could define __restrict as a
keyword equivalent to restrict. In fact that is probably what I
The compiler I am working with is a compiler I am developing designed to
dynamically analyze C code (you can read more about it at
http://runtimeverification.com/match if you are interested, although it's
not 100% relevant to this discussion). We use GLIBC's header files, but we
do not define the _
On 02/22/2016 01:46 PM, Dwight Guth wrote:
Currently there is a problem with the way the AC_C_RESTRICT macro behaves
if you are using GLIBC with a C99-compliant compiler that does not define
the __GNUC__ macro, but does define __restrict.
Which compiler is this, exactly? What does it define __r
Currently there is a problem with the way the AC_C_RESTRICT macro behaves
if you are using GLIBC with a C99-compliant compiler that does not define
the __GNUC__ macro, but does define __restrict. You can see this for
yourself by passing `CFLAGS="-U __GNUC__"` to a configure script that uses
it. Aut
