March 2012 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] How does this compare...
by Matthew Knepley 28 Mar '12

28 Mar '12

On Wed, Mar 28, 2012 at 9:39 PM, Hong Zhang <hzhang(a)mcs.anl.gov> wrote: > Matt: > >> to the new scalable MatMatMult() that is done in PETSc? Is it possible to >> even compare >> the flop rates sensibly? >> >> http://arxiv.org/abs/1203.1692 >> > "An Optimized Sparse Approximate Matrix Multiply" > computes Approximate matrix product for matrices with decay > ^^^^^^^^^^^^ > ^^^^^^^^^^ > It is for special application in chemistry(?), > not applicable for general sparse matrix product. > No comparison can be drawn to petsc's C=A*B. > This is the wrong conclusion. What he does is sparsify the result, so he is computing SOME sort of sparse matrix-vector product. The question is: Does his SpMV use the same algorithm as PETSc? That is why I asked. Matt > Hong > >> >> This is what Jeff is planning on using in his SciDAC. >> >> Matt >> >> -- >> What most experimenters take for granted before they begin their >> experiments is infinitely more interesting than any results to which their >> experiments lead. >> -- Norbert Wiener >> > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] How does this compare...
by Hong Zhang 28 Mar '12

28 Mar '12

Matt: > to the new scalable MatMatMult() that is done in PETSc? Is it possible to > even compare > the flop rates sensibly? > > http://arxiv.org/abs/1203.1692 > "An Optimized Sparse Approximate Matrix Multiply" computes Approximate matrix product for matrices with decay ^^^^^^^^^^^^ ^^^^^^^^^^ It is for special application in chemistry(?), not applicable for general sparse matrix product. No comparison can be drawn to petsc's C=A*B. Hong > > This is what Jeff is planning on using in his SciDAC. > > Matt > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener >

1 0

Re: [petsc-dev] GASM
by Mark F. Adams 28 Mar '12

28 Mar '12

Dmitry, I seem to have a problem with GASM. I have code like this to get an eigen estimate: ierr = PetscObjectReference( (PetscObject)subpc ); CHKERRQ(ierr); ierr = KSPSetPC( eksp, subpc ); CHKERRQ( ierr ); < snip > ierr = KSPDestroy( &eksp ); CHKERRQ(ierr); This 'subpc' has GASM and is used in the real solver. And I get this error when the real solver gets setup, after the above code: ==2070== Invalid read of size 4 ==2070== at 0x9F034C: PCSetUp_GASM (gasm.c:275) ==2070== by 0xA9620A: PCSetUp (precon.c:832) ==2070== by 0xB20EE5: KSPSetUp (itfunc.c:266) ==2070== by 0xA74975: PCSetUp_MG (mg.c:647) ==2070== by 0xA11A1B: PCSetUp_GAMG (gamg.c:803) ==2070== by 0xA9620A: PCSetUp (precon.c:832) ==2070== by 0xB20EE5: KSPSetUp (itfunc.c:266) ==2070== by 0xB22178: KSPSolve (itfunc.c:390) ==2070== by 0x95B8C0: kspsolve_ (itfuncf.c:219) ==2070== by 0x404E: MAIN__ (in ./ex54f) ==2070== by 0x4A6B: main (in ./ex54f) ==2070== Address 0x29e6ac0 is 32 bytes inside a block of size 108 free'd ==2070== at 0x19317D8: free (vg_replace_malloc.c:366) ==2070== by 0x865AD: PetscFreeAlign (mal.c:75) ==2070== by 0x9FAB7F: PCGASMDestroySubdomains (gasm.c:1309) ==2070== by 0x9F3AED: PCReset_GASM (gasm.c:536) ==2070== by 0xA8B322: PCReset (precon.c:80) ==2070== by 0xB270D0: KSPReset (itfunc.c:723) ==2070== by 0xB279BA: KSPDestroy (itfunc.c:760) ==2070== by 0xA1164D: PCSetUp_GAMG (gamg.c:779) ==2070== by 0xA9620A: PCSetUp (precon.c:832) ==2070== by 0xB20EE5: KSPSetUp (itfunc.c:266) ==2070== by 0xB22178: KSPSolve (itfunc.c:390) ==2070== by 0x95B8C0: kspsolve_ (itfuncf.c:219) ==2070== by 0x404E: MAIN__ (in ./ex54f) ==2070== by 0x4A6B: main (in ./ex54f) ==2070== [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Null argument, when expecting valid pointer! [0]PETSC ERROR: Null Object: Parameter # 1! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Development HG revision: e4ca525c39fd35cca849d095040a2de0488f347b HG Date: Fri Mar 23 22:45:44 2012 -0500 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: ./ex54f on a arch-maco named madams-macbk-3.home by markadams Wed Mar 28 21:20:16 2012 [0]PETSC ERROR: Libraries linked from /Users/markadams/Codes/petsc-dev/arch-macosx-gnu-O/lib [0]PETSC ERROR: Configure run at Sat Mar 24 09:45:16 2012 [0]PETSC ERROR: Configure options CXX="/sw/lib/gcc4.6/bin/g++-4 -malign-double" CC="/sw/lib/gcc4.6/bin/gcc-4 -malign-double" FC=/sw/lib/gcc4.6/bin/gfortran --download-parmetis=1 --download-metis=1 --download-hdf5=1 --download-hypre=1 --download-ml=1 --download-triangle=1 --with-x=0 --with-debugging=1 --download-mpich=1 PETSC_ARCH=arch-macosx-gnu-O --download-f-blas-lapack=1 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: ISSort() line 761 in /Users/markadams/Codes/petsc-dev/src/vec/is/interface/index.c [0]PETSC ERROR: PCSetUp_GASM() line 275 in /Users/markadams/Codes/petsc-dev/src/ksp/pc/impls/gasm/gasm.c THis error goes away if I comment out the above call to KSPDestroy. So it looks like KSPDestroy is destroying GASM (or part of it) even though I take a reference to it, to prevent this destruction. Any ideas? Mark > Mark, > > You should pass your subdomain ISs through the first IS list argument, and leave the second as PETSC_NULL. > In that case GASM assumes that the user passed in a nonoverlapping decomposition through the first list. > This is the behavior that GASM inherited from ASM and it isn't very well (or at all) documented in either. > Let me know if that doesn't fix the problem. > > Note also that you don't have to explicitly set overlap to 0: if the user sets not overlap PETSc won't try to increase it, > and if you set overlap to 0 it will not try to adjust the subdomains to make sure the overlap is 0. Both ASM and GASM simply assume that the user does the right thing and passes in a nonoverlapping decomposition. > > Incidentally, it may be time to change this API. I'm trying to debug a bad convergence problem with GASM -- inexplicably, it converges slower than ASM with a single process and multiple subdomains -- so now is a good time to mess with the code, while I still remember what's what. Another thing I've considered doing is reordering the subdomains internally (on demand only), to ensure a deadlock-free ordering of the subcomms. > > Dmitry. > > On Tue, Mar 27, 2012 at 6:28 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > This is why petsc-dev is better than a random list of email addresses. No one on your random list uses GASM > > > > Barry > > On Mar 27, 2012, at 4:49 PM, Mark F. Adams wrote: > > > I'm trying to make general non-overlapping domains in GASM. I create a vector of IS, each with the global indices of the equations in each block. > > > > I use code that looks like: > > > > ierr = PCSetType( subpc, PCGASM ); CHKERRQ(ierr); > > ierr = PCGASMSetLocalSubdomains( subpc, sz, PETSC_NULL, is ); CHKERRQ(ierr); > > ierr = PetscFree( is ); CHKERRQ(ierr); > > ierr = PCGASMSetOverlap( subpc, 0 ); CHKERRQ(ierr); > > > > In parallel, I get errors like this: > > > > [1]PETSC ERROR: gis_local contains -85 indices outside of gis! > > <snip> > > [1]PETSC ERROR: PCSetUp_GASM() line 332 in /Users/markadams/Codes/petsc-dev/src/ksp/pc/impls/gasm/gasm.c > > > > Anyone have any ideas on what I'm doing wrong here? I've checked the input and I think it is fine, > > > > Mark > >

1 0

Re: [petsc-dev] [petsc-users] Statistics on the popularity of PETSc
by Satish Balay 28 Mar '12

28 Mar '12

On Wed, 28 Mar 2012, Matthew Knepley wrote: > On Wed, Mar 28, 2012 at 11:54 AM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > > On Wed, 28 Mar 2012, Fredrik Heffer Valdmanis wrote: > > > > > Hi, > > > > > > Do you guys have any recent up-to-date numbers on for instance: > > > > > > - The number of PETSc downloads per month > > > - The number of projects that use PETSc > > > - The number of users of PETSc > > > > > > or anything else that may be used when discussing the popularity of > > PETSc? > > > I have seen some numbers on Matt's home page regarding hits on Google, > > > references on Google Books etc., so I can easily get updated such numbers > > > myself, but I would greatly appreciate it if you have anything to share > > > with me. > > > > I have the following statistics.. > > > > [2011] Total petsc tarball downloads : 43335 > > [2011] Unique machines requesting tarball downloads : 12979 > > [Today]Total unique e-mail ids in mailing lists : 1138 > > > > Regarding projects using PETSc - we have some incomplete info at: > > http://www.mcs.anl.gov/petsc/publications/index.html > > > We need this all the time. Can we put this somewhere we can all find it, > maybe with a methodology description. I had some manual process to get this info. But now I have a script [still a bit crude - and can do with improvements] for the download count part. I might still have to tweak this appropriately to get the relavent info in the future [financial year vs academic year or something else] Wrt mailing list email count - its still a bit manual process [and need admin access to the lists] I've added in the script that I've used to get the recent download count to petsc-dev at bin/maint/download-count.sh . It also has instructions on obtaining the email list count. Satish

1 0

Re: [petsc-dev] [petsc-users] Statistics on the popularity of PETSc
by Matthew Knepley 28 Mar '12

28 Mar '12

On Wed, Mar 28, 2012 at 11:54 AM, Satish Balay <balay(a)mcs.anl.gov> wrote: > On Wed, 28 Mar 2012, Fredrik Heffer Valdmanis wrote: > > > Hi, > > > > Do you guys have any recent up-to-date numbers on for instance: > > > > - The number of PETSc downloads per month > > - The number of projects that use PETSc > > - The number of users of PETSc > > > > or anything else that may be used when discussing the popularity of > PETSc? > > I have seen some numbers on Matt's home page regarding hits on Google, > > references on Google Books etc., so I can easily get updated such numbers > > myself, but I would greatly appreciate it if you have anything to share > > with me. > > I have the following statistics.. > > [2011] Total petsc tarball downloads : 43335 > [2011] Unique machines requesting tarball downloads : 12979 > [Today]Total unique e-mail ids in mailing lists : 1138 > > Regarding projects using PETSc - we have some incomplete info at: > http://www.mcs.anl.gov/petsc/publications/index.html We need this all the time. Can we put this somewhere we can all find it, maybe with a methodology description. Thanks, Matt > > Satish > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] cuda 4.1 errors with sm_20
by Satish Balay 27 Mar '12

27 Mar '12

On Tue, 27 Mar 2012, David Fuentes wrote: > Hi Satish, > > what version of cusp/thrust are you using with cuda 4.1 ? wrt cuda-4.1: thrust bundled with cuda 4.1 cusp-v0.3.1 wrt cuda-4.0 - the following worked for me. thrust-1.6.0 cusp-v0.3.1 Satish

1 0

Re: [petsc-dev] cuda 4.1 errors with sm_20
by Matthew Knepley 27 Mar '12

27 Mar '12

On Tue, Mar 27, 2012 at 10:44 PM, David Fuentes <fuentesdt(a)gmail.com> wrote: > Hi Satish, > > what version of cusp/thrust are you using with cuda 4.1 ? > Thrust is packaged with 4.1 and that is the one you should use (just --with-thrust). We use the latest pull from CUSP, which is 2.00 Matt > > On Tue, Mar 27, 2012 at 10:23 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > >> Chetan, thanks for the note. I guess I should have first searched >> petsc archives :). >> >> Looks like we default to -g3 for gcc, but -g for g++/gfortran [due to >> bugs in some version of these compilers]. However -g3 is usefull for >> debugging macros - so its a good default. >> >> For now - I'm switching the default from -g3 to -g for cuda >> builds [one can always override this with COPTFLAGS options] >> >> Satish >> >> On Tue, 27 Mar 2012, Chetan Jhurani wrote: >> >> > Satish, >> > >> > This is because of -g3 option to nvcc. Attaching my >> > earlier mail to petsc-maint. >> > >> > Chetan >> > >> > > -----Original Message----- >> > > From: petsc-dev-bounces(a)mcs.anl.gov [mailto: >> petsc-dev-bounces(a)mcs.anl.gov] On Behalf Of Satish Balay >> > > Sent: Tuesday, March 27, 2012 7:31 PM >> > > To: petsc-dev(a)mcs.anl.gov >> > > Subject: [petsc-dev] cuda 4.1 errors with sm_20 >> > > >> > > I get errors with building petsc using cuda-4.1 with 'sm_20' on >> > > linux. Reverting to cuda-4.0 [with cusp-v0.3.1, thrust-1.6.0] >> > > overcomes this issue. >> > > >> > > >From >> > > >> http://developer.download.nvidia.com/compute/cuda/4_1/rel/toolkit/docs/CUDA… >> > > Errata.txt >> > > * For target architecture sm_2x, a new compiler component 'cicc' is >> used instead of 'nvopencc'. >> > > >> > > So the new compiler used for sm20 - 'cicc' is perhaps buggy. >> > > >> > > Matt,Sean or Barry, Do you see the same behavior on Mac? >> > > >> > > Satish >> > > --------------------------- >> > > balay@bb30:~/petsc-dev/src/mat/impls/aij/seq/seqcusp>nvcc -g >> -arch=sm_20 -c --compiler-options="-Wall >> > > -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 >> -fno-inline -O0 -I/home/balay/petsc- >> > > dev/include -I/home/balay/petsc-dev/arch-cuda-double/include >> -I/usr/local/cuda/include - >> > > I/home/balay/petsc-dev/arch-cuda-double/include/txpetscgpu/include >> -I/usr/local/cusp-v0.3.1/ - >> > > D__INSDIR__=src/mat/impls/aij/seq/seqcusp/" aijcusp.cu >> > > <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>(129): error: "__unix__" is predefined; attempted >> redefinition ignored >> > > >> > > <built-in>(130): error: "unix" is predefined; attempted redefinition >> ignored >> > > >> > > 7 errors detected in the compilation of >> "/tmp/tmpxft_00003334_00000000-7_aijcusp.cpp3.i". >> > >> >> > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] cuda 4.1 errors with sm_20
by David Fuentes 27 Mar '12

27 Mar '12

Hi Satish, what version of cusp/thrust are you using with cuda 4.1 ? On Tue, Mar 27, 2012 at 10:23 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > Chetan, thanks for the note. I guess I should have first searched > petsc archives :). > > Looks like we default to -g3 for gcc, but -g for g++/gfortran [due to > bugs in some version of these compilers]. However -g3 is usefull for > debugging macros - so its a good default. > > For now - I'm switching the default from -g3 to -g for cuda > builds [one can always override this with COPTFLAGS options] > > Satish > > On Tue, 27 Mar 2012, Chetan Jhurani wrote: > > > Satish, > > > > This is because of -g3 option to nvcc. Attaching my > > earlier mail to petsc-maint. > > > > Chetan > > > > > -----Original Message----- > > > From: petsc-dev-bounces(a)mcs.anl.gov [mailto: > petsc-dev-bounces(a)mcs.anl.gov] On Behalf Of Satish Balay > > > Sent: Tuesday, March 27, 2012 7:31 PM > > > To: petsc-dev(a)mcs.anl.gov > > > Subject: [petsc-dev] cuda 4.1 errors with sm_20 > > > > > > I get errors with building petsc using cuda-4.1 with 'sm_20' on > > > linux. Reverting to cuda-4.0 [with cusp-v0.3.1, thrust-1.6.0] > > > overcomes this issue. > > > > > > >From > > > > http://developer.download.nvidia.com/compute/cuda/4_1/rel/toolkit/docs/CUDA… > > > Errata.txt > > > * For target architecture sm_2x, a new compiler component 'cicc' is > used instead of 'nvopencc'. > > > > > > So the new compiler used for sm20 - 'cicc' is perhaps buggy. > > > > > > Matt,Sean or Barry, Do you see the same behavior on Mac? > > > > > > Satish > > > --------------------------- > > > balay@bb30:~/petsc-dev/src/mat/impls/aij/seq/seqcusp>nvcc -g > -arch=sm_20 -c --compiler-options="-Wall > > > -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 > -fno-inline -O0 -I/home/balay/petsc- > > > dev/include -I/home/balay/petsc-dev/arch-cuda-double/include > -I/usr/local/cuda/include - > > > I/home/balay/petsc-dev/arch-cuda-double/include/txpetscgpu/include > -I/usr/local/cusp-v0.3.1/ - > > > D__INSDIR__=src/mat/impls/aij/seq/seqcusp/" aijcusp.cu > > > <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>(129): error: "__unix__" is predefined; attempted > redefinition ignored > > > > > > <built-in>(130): error: "unix" is predefined; attempted redefinition > ignored > > > > > > 7 errors detected in the compilation of > "/tmp/tmpxft_00003334_00000000-7_aijcusp.cpp3.i". > > > >

1 0

Re: [petsc-dev] cuda 4.1 errors with sm_20
by Satish Balay 27 Mar '12

27 Mar '12

Chetan, thanks for the note. I guess I should have first searched petsc archives :). Looks like we default to -g3 for gcc, but -g for g++/gfortran [due to bugs in some version of these compilers]. However -g3 is usefull for debugging macros - so its a good default. For now - I'm switching the default from -g3 to -g for cuda builds [one can always override this with COPTFLAGS options] Satish On Tue, 27 Mar 2012, Chetan Jhurani wrote: > Satish, > > This is because of -g3 option to nvcc. Attaching my > earlier mail to petsc-maint. > > Chetan > > > -----Original Message----- > > From: petsc-dev-bounces(a)mcs.anl.gov [mailto:[email protected]] On Behalf Of Satish Balay > > Sent: Tuesday, March 27, 2012 7:31 PM > > To: petsc-dev(a)mcs.anl.gov > > Subject: [petsc-dev] cuda 4.1 errors with sm_20 > > > > I get errors with building petsc using cuda-4.1 with 'sm_20' on > > linux. Reverting to cuda-4.0 [with cusp-v0.3.1, thrust-1.6.0] > > overcomes this issue. > > > > >From > > http://developer.download.nvidia.com/compute/cuda/4_1/rel/toolkit/docs/CUDA… > > Errata.txt > > * For target architecture sm_2x, a new compiler component 'cicc' is used instead of 'nvopencc'. > > > > So the new compiler used for sm20 - 'cicc' is perhaps buggy. > > > > Matt,Sean or Barry, Do you see the same behavior on Mac? > > > > Satish > > --------------------------- > > balay@bb30:~/petsc-dev/src/mat/impls/aij/seq/seqcusp>nvcc -g -arch=sm_20 -c --compiler-options="-Wall > > -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -fno-inline -O0 -I/home/balay/petsc- > > dev/include -I/home/balay/petsc-dev/arch-cuda-double/include -I/usr/local/cuda/include - > > I/home/balay/petsc-dev/arch-cuda-double/include/txpetscgpu/include -I/usr/local/cusp-v0.3.1/ - > > D__INSDIR__=src/mat/impls/aij/seq/seqcusp/" aijcusp.cu > > <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>(129): error: "__unix__" is predefined; attempted redefinition ignored > > > > <built-in>(130): error: "unix" is predefined; attempted redefinition ignored > > > > 7 errors detected in the compilation of "/tmp/tmpxft_00003334_00000000-7_aijcusp.cpp3.i". >

1 0

Re: [petsc-dev] cuda 4.1 errors with sm_20
by Chetan Jhurani 27 Mar '12

27 Mar '12

Satish, This is because of -g3 option to nvcc. Attaching my earlier mail to petsc-maint. Chetan > -----Original Message----- > From: petsc-dev-bounces(a)mcs.anl.gov [mailto:[email protected]] On Behalf Of Satish Balay > Sent: Tuesday, March 27, 2012 7:31 PM > To: petsc-dev(a)mcs.anl.gov > Subject: [petsc-dev] cuda 4.1 errors with sm_20 > > I get errors with building petsc using cuda-4.1 with 'sm_20' on > linux. Reverting to cuda-4.0 [with cusp-v0.3.1, thrust-1.6.0] > overcomes this issue. > > >From > http://developer.download.nvidia.com/compute/cuda/4_1/rel/toolkit/docs/CUDA… > Errata.txt > * For target architecture sm_2x, a new compiler component 'cicc' is used instead of 'nvopencc'. > > So the new compiler used for sm20 - 'cicc' is perhaps buggy. > > Matt,Sean or Barry, Do you see the same behavior on Mac? > > Satish > --------------------------- > balay@bb30:~/petsc-dev/src/mat/impls/aij/seq/seqcusp>nvcc -g -arch=sm_20 -c --compiler-options="-Wall > -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -fno-inline -O0 -I/home/balay/petsc- > dev/include -I/home/balay/petsc-dev/arch-cuda-double/include -I/usr/local/cuda/include - > I/home/balay/petsc-dev/arch-cuda-double/include/txpetscgpu/include -I/usr/local/cusp-v0.3.1/ - > D__INSDIR__=src/mat/impls/aij/seq/seqcusp/" aijcusp.cu > <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>(129): error: "__unix__" is predefined; attempted redefinition ignored > > <built-in>(130): error: "unix" is predefined; attempted redefinition ignored > > 7 errors detected in the compilation of "/tmp/tmpxft_00003334_00000000-7_aijcusp.cpp3.i".

1 0