Hello,
I wanted to use PaStix and have the problem, that the debugging version works
and PETSc compiled with option --with-debugging=0 gives following error:
what could be wrong?
++
+ PaStiX : Parallel Sparse
Perhaps you can try running in valgrind to see here the problem is.
You can also try --with-debugging=0 COPTFLAGS='-g -O' - and see if it
crashes. If so - run in a debugger to determine the problem.
Satish
On Tue, 20 Oct 2009, Andreas Grassl wrote:
Hello,
I wanted to use PaStix and have
Hello,
I would like to know some information about GMRES performance in PETSc
if you have any experience.
I am running a parallel test case(9300 cells) comparing cpu time using
by solvers in Petsc. While BICGSTAB was doing 0.9 sec, GMRES 15 sec
with the same preconditioner(Additive
their experiments
lead.
-- Norbert Wiener
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20091020/f7c08ec5/attachment.htm
Run with valgrind (www.valgrind.org). Valgrind is simply the MOST
important software tool for C/C++ developers available in the past 10+
years.
First run the debug version in valgrind, because often there can be
memory errors that don't crash the program and valgrind will find them.
On Oct 20, 2009, at 9:52 AM, jarunan at ascomp.ch wrote:
Hello,
I would like to know some information about GMRES performance in
PETSc if you have any experience.
I am running a parallel test case(9300 cells) comparing cpu time
using by solvers in Petsc. While BICGSTAB was doing 0.9
,
Keita Teranishi
Scientific Library Group
Cray, Inc.
keita at cray.com
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20091020/8df0d63e/attachment.htm
make ACTION=lib tree
Barry
On Oct 20, 2009, at 4:37 PM, Keita Teranishi wrote:
Hi,
In PETSc, makefile in the top directory produces make.log, which
shows only file names that have been compiled, but we?d like to see
more detailed output like interaction with compiler commands
Usually the header at the begining lists these compiler options
separately. But if you want the extra info - you can do:
make ACTION=lib tree
Note: this is not exactly the same build as the default build ['libfast'
attempts to compile multiple files with a sigle command - whereas
'lib' does one
