[petsc-dev] autogeneration of petscconf.h for C, C++ and Fortran

[Jed Brown]

On Fri, May 13, 2011 at 04:43, Barry Smith <bsmith at mcs.anl.gov> wrote:

> On occasion the same options in petscconf.h don't work for both C and C++
> compilers, for example for __intel_fast_memcpy().


This is just insane, but I thought the compiler automatically expanded
normal memcpy to __intel_fast_memcpy. I just checked and my Intel C and C++
compilers (versions 10 and 11) do this automatically at -O2 and above.
Should PETSc ever be calling it directly?

 Should we instead generate three files one for each language?


If it's really necessary, why not put both in the same header guarded by
#ifdef __cplusplus ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110513/550e6c7f/attachment.html>