Autogenerate Fortran stubs for PCShellSetContext

Hg-commit: 533ba945fa131a409d3fcfa890da6e629a563a8f

Correct number of fortran pointers

Hg-commit: 4b88773860a3454337070c5863cc56691239632e

PCShell API change

PCShell functions now have PC as first argument, as in

apply(PC,Vec,Vec)

instead of the user context. The user context should be obtained with
PCShellGetContext, as with MatS

PCShell API change

PCShell functions now have PC as first argument, as in

apply(PC,Vec,Vec)

instead of the user context. The user context should be obtained with
PCShellGetContext, as with MatShell.

Hg-commit: ba1711e68e6d85b2619b5ebb90e20f446ebdaf25

show more ...

When KSPRICHARDSON is used without a KSP monitor and the PC has a PCApplyRichardson() then
ksp->its and converged reason are properly set to indicate type of convergence.

Also with HYPRE BoomerAMG

When KSPRICHARDSON is used without a KSP monitor and the PC has a PCApplyRichardson() then
ksp->its and converged reason are properly set to indicate type of convergence.

Also with HYPRE BoomerAMG when used as a solver (with KSPRichardson) the KSP convergence
criteria is passed down to BoomAMG and replaces the default (usually 0.0) criteria we normally
pass to BoomerAMG (for when we use BoomerAMG as a preconditioner.

Keita,

Thanks for pointing this out. This is a "feature" of some of the preconditioners when used with
Richardson. We call the preconditioner with a number of iterations directly and the preconditioner
decides when to exit (rather than all other cases where KSP decides), hence we did not have
information about the number of iterations. So in previous versions we did not set the ksp->its;
petsc-dev was changed to set ksp->its to the maximum number of iterations requested in the
preconditioner.

This too is not really correct because some preconditioners when used with Richardson
(specifically PCMG and hypre's BoomerAMG) will do the convergence test internally and
may not use the maximum number of iterations requested. I will modify petsc-dev today to
collect this information back from the preconditioner and pass it back correctly to ksp->its.

Hg-commit: d8d04f2052ab2294999b137bb681449db81389c7

show more ...

fixed ex15f.F that uses PCSHELL to also use PCShellSetSetUp() and PCShellSetDestroy()

Hg-commit: 303da9e00c1aec557afcb32664583af7c55b997f

finished converting Shellpc Fortran interface to use fortran_func_pointers
changed conversion of fortran_func_pointers for storing contexts to immediately cast to void*

Hg-commit: fe23f661c1ebf8b372

finished converting Shellpc Fortran interface to use fortran_func_pointers
changed conversion of fortran_func_pointers for storing contexts to immediately cast to void*

Hg-commit: fe23f661c1ebf8b37267813b8a021aeafbee732d

show more ...

mv zpetsc.h (a meaningless name) to fortranimpl.h (a slightly more meaningful name)

Hg-commit: d2687f12f92bff49ceff434100d018f6898829c3

petsc-maint 16799 ==6657== Conditional jump or move depends on uninitialised value(s) ==6657== at 0x8735AD1: petscoptionsgetstring_ (in /home/go

petsc-maint 16799 ==6657== Conditional jump or move depends on uninitialised value(s) ==6657== at 0x8735AD1: petscoptionsgetstring_ (in /home/gormo/fluidity/trunk/bin/petsc_readnsolve) ==6657== by 0x80F426D: petsc_readnsolve_options.878 (petsc_readnsolve.F90:264) ==6657== by 0x80F197C: petsc_readnsolve_ (petsc_readnsolve.F90:73) ==6657== by 0x80F18AD: main (petsc_readnsolve_main.cpp:28)

moved zpetsc.h to private/zpetsc.h

changed Fortran interface function PetscOptionsGetXXX functions to allow passing
PETSC_NULL_TRUTH as flag argument

Hg-commit: a08dc4d2e15e97c0d3849b1cb02e6c1b0214b0c8

show more ...

changed bmake/common everywhere to conf
fixed a little more for new install system

Hg-commit: 1aa781ff09e652ebafd6f016d84e88c15ea650f1