This is a known problem. Intel changed their complex dot a while ago
causing grief. Perhaps Apple follows the Intel blas libraries since they are
in bed with Intel.
Anyways, yes a proper set of configure tests is needed for different
versions of complex (double and single) dot and t
On Sat, Feb 18, 2012 at 5:34 PM, Jack Poulson wrote:
> I think I mentioned this to several PETSc folks two years ago. It is a bad
> idea to return complex numbers from Fortran, as there is no portable
> solution as far as I know; some compilers need you to declare it as
>
> complex zdotc_( )
>
>
I think I mentioned this to several PETSc folks two years ago. It is a bad
idea to return complex numbers from Fortran, as there is no portable
solution as far as I know; some compilers need you to declare it as
complex zdotc_( )
some as
void zdotc_( , complex* z )
and I think I ran into probl
We have a problem with complex dot product on OSX. Here is the easiest way
to see it (I think):
knepley:/PETSc3/petsc/petsc-dev$ ./arch-complex-fftw-debug/lib/ex5-obj/ex5
-snes_monitor
./arch-complex-fftw-debug/lib/ex5-obj/ex5 -snes_monitor
0 SNES Function norm 0.e+00
With the debug
