I would to propose some changes to error checking macros for optimized builds.
1.- SETERRQXXX: define them as
#define SETERRQ[1|2|..](ierr,...) return ierr
2.- CHKERRQ: define them as
#define CHKERRQ(ierr) if (ierr) return ierr
For (1), it should be no performace impact. For (2), the extra
On Nov 23, 2007 10:25 AM, Lisandro Dalcin dalcinl at gmail.com wrote:
I would to propose some changes to error checking macros for optimized builds.
1.- SETERRQXXX: define them as
#define SETERRQ[1|2|..](ierr,...) return ierr
I think this is fine. However for it to matter, you need 2.
Lisandro,
There are actually two separate concerns: optimized builds and
error checking.
--with-errorchecking and --with-debugging I would like to keep them
separate.
Currently --with-errorchecking has an on or off value and --with-
debugging has an on or off value
If you are
On 11/23/07, Barry Smith bsmith at mcs.anl.gov wrote:
There are actually two separate concerns: optimized builds and
error checking.
--with-errorchecking and --with-debugging I would like to keep them
separate.
Me too.
Currently --with-errorchecking has an on or off value and --with-
I've achieved considerable progress in making petsc4py provide
cross-language interoperable in the context of PETSc applications.
I've implemented some new types for Mat, KSP, PC, SNES and TS. Those
new type implementations enables dynamically use a Python class
implementing some specific
On 11/23/07, Matthew Knepley knepley at gmail.com wrote:
Yes, we should definitely do this. I think I already have the support for
linking to the Python library somewhere.
Perhaps I will also ask in the near future for adding two 'slots' in
the base PetscObject structure for better
On 11/23/07, Barry Smith bsmith at mcs.anl.gov wrote:
Likely just an oversight, you can add it.
Should I push this in release-2.3.3 ?? I'm almost sure this will not
affect currently implemented matrix types, none of them seems to be
filling ops-setfromoptions.
Barry
On Nov 23, 2007,
Fine with me.
On Nov 23, 2007, at 4:47 PM, Lisandro Dalcin wrote:
On 11/23/07, Barry Smith bsmith at mcs.anl.gov wrote:
Likely just an oversight, you can add it.
Should I push this in release-2.3.3 ?? I'm almost sure this will not
affect currently implemented matrix types, none of
I have run the example.
BTW: run with -snes_monitor the nonlinear convergence is terribly
slow.
BTW: I have added a --download-numpy and --download-petsc4py to
petsc-dev. Preliminary version
uses the SVN versions. Eventually I'd like it to auto-select the
correct version.
Can we move maint to bin/maint?
Barry
Can we move python/PETSc and python/BuildSystem to config/PETSc and
config/BuildSystem and
remove python directory?
Reason: a directory should not be named after the language it uses,
PETSc and BuildSystem
are config stuff and the other stuff in python is no longer used.
Barry
11 matches
Mail list logo