<div class="gmail_extra">On Fri, Apr 27, 2012 at 11:53 AM, Daniel Lowell <span dir="ltr"><<a href="mailto:redratio1@gmail.com" target="_blank">redratio1@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra">Even with the new build system I still had to go through and eliminate the -g3 in petscvariables</div><div class="gmail_extra"><br></div><div class="gmail_extra">CC_FLAGS = -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -fno-inline -O0</div>
<div class="gmail_extra">PCC_LINKER_FLAGS = -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -fno-inline -O0</div><div class="gmail_extra"><div class="gmail_extra">PCC_FLAGS = -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -fno-inline -O0</div>
</div></blockquote><div><br></div><div>I just ran this last night. There were no more -g3's. As Satish said, send logs.</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 23, 2012 at 4:43 PM, Daniel Lowell <span dir="ltr"><<a href="mailto:redratio1@gmail.com" target="_blank">redratio1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sending the make.log to petsc-maint now.<div><div><br><br><div class="gmail_quote">On Mon, Apr 23, 2012 at 4:38 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
but you missed copy/pasting the actual compile command. So incomplete info here..<br>
<div><div><br>
satish<br>
<br>
On Mon, 23 Apr 2012, Daniel Lowell wrote:<br>
<br>
> I added -v in the local folder's makefile to produce verbose output.<br>
><br>
> On Mon, Apr 23, 2012 at 4:33 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>> wrote:<br>
><br>
> > Hm - we've seen these errors with -g3 but not with -g. Are you sure<br>
> > there is no '-g3' somewhere on the compile command?<br>
> ><br>
> > With latest petsc-dev/buildsystem one should not see -g3 [set by configure]<br>
> ><br>
> > Also - why is there 'cicc' in a petsc build?<br>
> ><br>
> > Satish<br>
> ><br>
> > On Mon, 23 Apr 2012, Daniel Lowell wrote:<br>
> ><br>
> > > Hi all,<br>
> > ><br>
> > ><br>
> > > Has anyone run into any problems with NVCC 4.1 or .42 on PETSc with<br>
> > > arch=sm_20?<br>
> > > I have having real issues with it. I keep getting this:<br>
> > ><br>
> > > #$ cicc -arch compute_20 -m64 -ftz=0 -prec_div=1 -prec_sqrt=1 -fmad=1 -g<br>
> > > -O0 "/tmp/tmpxft_00000b8b_00000000-10_vecgpu"<br>
> > > "/tmp/tmpxft_00000b8b_00000000-7_vecgpu.cpp3.i" -o<br>
> > > "/tmp/tmpxft_00000b8b_00000000-2_vecgpu.ptx"<br>
> > > <built-in>(2): error: "__STDC_HOSTED__" is predefined; attempted<br>
> > > redefinition ignored<br>
> > ><br>
> > > <built-in>(8): error: "__WCHAR_TYPE__" is predefined; attempted<br>
> > > redefinition ignored<br>
> > ><br>
> > > <built-in>(115): error: "__x86_64" is predefined; attempted redefinition<br>
> > > ignored<br>
> > ><br>
> > > <built-in>(116): error: "__x86_64__" is predefined; attempted<br>
> > redefinition<br>
> > > ignored<br>
> > ><br>
> > > <built-in>(126): error: "__linux__" is predefined; attempted redefinition<br>
> > > ignored<br>
> > ><br>
> > > <built-in>(128): error: "__unix__" is predefined; attempted redefinition<br>
> > > ignored<br>
> > ><br>
> > > 6 errors detected in the compilation of<br>
> > > "/tmp/tmpxft_00000b8b_00000000-7_vecgpu.cpp3.i".<br>
> > > # --error 0x1 --<br>
> > ><br>
> > ><br>
> > > 4.0 works fine, no issues.<br>
> > > 4.0 version uses the older nvopencc, in 4.1 and 4.2 they use something<br>
> > > called cicc, for target architecture sm_2x. Of course it does no mention<br>
> > > cicc in the updated nvcc documentation at all.<br>
> > ><br>
> > > Tried 4.2 with GCC 4.3 and 4.4 without any difference in behavior.<br>
> > ><br>
> > ><br>
> > > PETSc configuration script:<br>
> > ><br>
> > > MPI_DIR="--with-mpi-dir=$MPICH2_HOME"<br>
> > > LAD="--download-f-blas-lapack=yes"<br>
> > > CUD="--with-cuda-dir=/soft/cuda-4.2/cuda"<br>
> > > ./config/configure.py $MPI_DIR $LAD $CUD \<br>
> > > --with-debugging=1 \<br>
> > > --with-cudac="nvcc -m64 -g -G" \<br>
> > > --with-precision=double \<br>
> > > --with-clanguage=c \<br>
> > > --with-cuda-arch=sm_20<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></div><span class="HOEnZb"><font color="#888888"><span><font color="#888888">-- <br>Daniel Lowell<br>
<br>
</font></span></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Daniel Lowell<br><br>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>
</div>