[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_C_RESTRICT
From: |
Ralf Wildenhues |
Subject: |
Re: AC_C_RESTRICT |
Date: |
Tue, 17 Mar 2009 07:46:29 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Jeff Squyres wrote on Mon, Mar 16, 2009 at 11:54:13PM CET:
>
> It seems that AC_C_RESTRICT can sometimes find "restrict" for the PGI C
> compiler, but it can sometimes find "__restrict". Both of these values
> work for the PGI C compiler, but only "__restrict" works for the PGI C++
> compiler.
The Autoconf test tries __restrict first, at least the current code
does. Can you please find the bits in the config.log file that show
why the test fails with __restrict but later passes with restrict,
for the PGI C compiler?
> - should there be an AC_CXX_RESTRICT test? E.g., perhaps the output of
> AC_C_RESTRICT and AC_CXX_RESTRICT tests would be protected with
> appropriate #if's that determine if you're compiling in C or C++.
I don't see the need for that yet: both Sun and PGI compiler suites have
a common denominator; only if you want to mix-and-match compilers from
different suites, then we need to go all the way.
Thanks,
Ralf
Re: AC_C_RESTRICT,
Ralf Wildenhues <=