Re: [Libmesh-devel] Compiling libMesh with XL compilers

2013-11-02 Thread Francesco Ballarin
Hi John, thanks. a) I tried building PETSc with --with-clanguage=cxx as you suggested, my configure options are now === ./configure --with-mpi-dir=/bgsys/drivers/ppcfloor/comm/xl/ --with-clanguage=cxx --with-blas-lapack-lib=/opt/ibmmath/essl/5.1/lib64/libesslbg.a --with-make-np=8 --prefix=$PETSC_I

Re: [Libmesh-devel] Compiling libMesh with XL compilers

2013-11-02 Thread Kirk, Benjamin (JSC-EG311)
On Nov 1, 2013, at 11:35 PM, "John Peterson" wrote: > Why on earth would IBM do this? It differs from literally every other > compiler that I've ever seen. I don't know if there's a built-in autoconf > test for "how to #define stuff on the compile line" but that seems like > that's what we'd

Re: [Libmesh-devel] Metis memory usage

2013-11-02 Thread Kirk, Benjamin (JSC-EG311)
On Nov 1, 2013, at 11:15 PM, "John Peterson" wrote: > Finally, note that we call adjncy.reserve(graph_size); where graph_size=48M. > This was most likely done for speed, but it means that the full memory for > both 'graph' and 'adjncy' are required at the same time. We could instead > try le

Re: [Libmesh-devel] Metis memory usage

2013-11-02 Thread Kirk, Benjamin (JSC-EG311)
On Nov 2, 2013, at 7:42 AM, "Kirk, Benjamin (JSC-EG311)" wrote: > On Nov 1, 2013, at 11:15 PM, "John Peterson" wrote: > >> Finally, note that we call adjncy.reserve(graph_size); where graph_size=48M. >> This was most likely done for speed, but it means that the full memory for >> both 'grap

Re: [Libmesh-devel] Compiling libMesh with XL compilers

2013-11-02 Thread John Peterson
> On Nov 2, 2013, at 5:13 AM, Francesco Ballarin > wrote: > > Hi John, > thanks. > > a) I tried building PETSc with --with-clanguage=cxx as you suggested, my > configure options are now Sorry, didn't mean to suggest _trying_ this, it shouldn't be necessary. Was just wondering if this was

Re: [Libmesh-devel] Compiling libMesh with XL compilers

2013-11-02 Thread John Peterson
> On Nov 2, 2013, at 5:13 AM, Francesco Ballarin > wrote: > > Hi John, > thanks. > > a) I tried building PETSc with --with-clanguage=cxx as you suggested, my > configure options are now > === > ./configure --with-mpi-dir=/bgsys/drivers/ppcfloor/comm/xl/ > --with-clanguage=cxx > --with-blas

Re: [Libmesh-devel] Metis memory usage

2013-11-02 Thread John Peterson
> On Nov 2, 2013, at 7:01 AM, "Kirk, Benjamin (JSC-EG311)" > wrote: > >> On Nov 2, 2013, at 7:42 AM, "Kirk, Benjamin (JSC-EG311)" >> wrote: >> >>> On Nov 1, 2013, at 11:15 PM, "John Peterson" wrote: >>> >>> Finally, note that we call adjncy.reserve(graph_size); where >>> graph_size=48M.

Re: [Libmesh-devel] Compiling libMesh with XL compilers

2013-11-02 Thread Francesco Ballarin
There is a native autotools installation, but running autoreconf -iv --force, configure again and make again does not fix the "-WF,-D" part. It's no big deal anyway for me in this moment, there is just one file affected (contrib/exodusii/v5.22/exodus/forbind/src/libdbg_la-addrwrap.lo) On Sat, Nov

Re: [Libmesh-devel] Compiling libMesh with XL compilers

2013-11-02 Thread Francesco Ballarin
Yes, it builds a static lib. I guess I could have also added "--with-shared-libraries=0", just to be sure. Anyway I have that option in my "production" installation of PETSc (among other flags related to third party libraries, which I temporarily disabled to keep things as simple as possible), but

Re: [Libmesh-devel] Metis memory usage

2013-11-02 Thread Kirk, Benjamin (JSC-EG311)
On Nov 2, 2013, at 9:03 AM, John Peterson wrote: > Damn... Yeah this would clearly help the most for the parallel runs. No > reason to really optimize anything else until that's implemented! So that is done now in the branch... I'll still work to refractor the adjacency build, but that'll ta

Re: [Libmesh-devel] Metis memory usage

2013-11-02 Thread John Peterson
On Sat, Nov 2, 2013 at 8:21 AM, Kirk, Benjamin (JSC-EG311) < benjamin.k...@nasa.gov> wrote: > On Nov 2, 2013, at 9:03 AM, John Peterson > wrote: > > > Damn... Yeah this would clearly help the most for the parallel runs. No > reason to really optimize anything else until that's implemented! > >

Re: [Libmesh-devel] Metis memory usage

2013-11-02 Thread John Peterson
On Sat, Nov 2, 2013 at 12:42 PM, John Peterson wrote: > > > > On Sat, Nov 2, 2013 at 8:21 AM, Kirk, Benjamin (JSC-EG311) < > benjamin.k...@nasa.gov> wrote: > >> On Nov 2, 2013, at 9:03 AM, John Peterson >> wrote: >> >> > Damn... Yeah this would clearly help the most for the parallel runs. >> N