Hm - we've seen these errors with -g3 but not with -g. Are you sure there is no '-g3' somewhere on the compile command?
With latest petsc-dev/buildsystem one should not see -g3 [set by configure] Also - why is there 'cicc' in a petsc build? Satish On Mon, 23 Apr 2012, Daniel Lowell wrote: > Hi all, > > > Has anyone run into any problems with NVCC 4.1 or .42 on PETSc with > arch=sm_20? > I have having real issues with it. I keep getting this: > > #$ cicc -arch compute_20 -m64 -ftz=0 -prec_div=1 -prec_sqrt=1 -fmad=1 -g > -O0 "/tmp/tmpxft_00000b8b_00000000-10_vecgpu" > "/tmp/tmpxft_00000b8b_00000000-7_vecgpu.cpp3.i" -o > "/tmp/tmpxft_00000b8b_00000000-2_vecgpu.ptx" > <built-in>(2): error: "__STDC_HOSTED__" is predefined; attempted > redefinition ignored > > <built-in>(8): error: "__WCHAR_TYPE__" is predefined; attempted > redefinition ignored > > <built-in>(115): error: "__x86_64" is predefined; attempted redefinition > ignored > > <built-in>(116): error: "__x86_64__" is predefined; attempted redefinition > ignored > > <built-in>(126): error: "__linux__" is predefined; attempted redefinition > ignored > > <built-in>(128): error: "__unix__" is predefined; attempted redefinition > ignored > > 6 errors detected in the compilation of > "/tmp/tmpxft_00000b8b_00000000-7_vecgpu.cpp3.i". > # --error 0x1 -- > > > 4.0 works fine, no issues. > 4.0 version uses the older nvopencc, in 4.1 and 4.2 they use something > called cicc, for target architecture sm_2x. Of course it does no mention > cicc in the updated nvcc documentation at all. > > Tried 4.2 with GCC 4.3 and 4.4 without any difference in behavior. > > > PETSc configuration script: > > MPI_DIR="--with-mpi-dir=$MPICH2_HOME" > LAD="--download-f-blas-lapack=yes" > CUD="--with-cuda-dir=/soft/cuda-4.2/cuda" > ./config/configure.py $MPI_DIR $LAD $CUD \ > --with-debugging=1 \ > --with-cudac="nvcc -m64 -g -G" \ > --with-precision=double \ > --with-clanguage=c \ > --with-cuda-arch=sm_20 > > > > >
