On 06/19/2010 10:13 AM, Ralf Wildenhues wrote:
> I don't really that we can set this automatically, due to the binary
> incompatibility, so we may need to resort to C++ specific restrict
> setting based on __cplusplus.  Thoughts?

We've already tried hard to make AC_C_RESTRICT pick a value that will
work for both C and C++ compilers, as long as both compilers are from
the same vendor.  If we can't come up with anything better than
__cplusplus, then I guess that will have to do, but is there any way we
can detect this at configure time while probing only one of the two
compilers?  Also, we already have a __SUNPRO_CC-specific workaround for
two different definitions of restrict for the C/C++ pair of the Sunpro
compiler suite - is there a another preprocessor macro we can reliably
use to identify this Tru64 vendor compiler pair?

-- 
Eric Blake   ebl...@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to