minor
change MatSolverType to be a const char* typedef to match other XXTypeCommit-type: style-fixReported-by: Franck Houssen <franck.houssen@inria.fr>
Fix name MatSolverPackage since it is better to be consistent and use the terminology Type.Commit-type: style-fix, documentation
Merge branch 'maint'
fix terrible name for routines that view the info level of matrixResulted in links from MatFactorInfo to MatFactorInfo_XXX() which are really unrelated routinesCommit-type: documentation
fix typo in manual page that propogated with cut and paste to many manual pagesCommit-type: documentationReported-by: apostol <apostol.faliagas@gmail.com>
UMFPack errors on a zero size matrix, so just bypass UMFPack on calls with zero size matrixCommit-type: featureReported-by: nightly testsThanks-to: Mark Adams <mfadams@lbl.gov>
Remove the use and definition of __FUNCT__ throughout the codeSince all modern C/C++ compilers provide this functionality we no longer need to provide it manually in PETScTime: 1.5 hoursThanks-t
Remove the use and definition of __FUNCT__ throughout the codeSince all modern C/C++ compilers provide this functionality we no longer need to provide it manually in PETScTime: 1.5 hoursThanks-to: Andreas Mang <andreas@ices.utexas.edu>
show more ...
changes to cholmod and umfpack to avoid the unneccesary use of spptr andsimplify the implimation of external solver packages
Fix null output from PCFactorGetMatSolverPackage();Reported-by: Jose E. Roman <jroman@dsic.upv.es>
Tao Fortran stubs not properly marked with PETSC_EXTERN so would not work with multiple libraries and visibility turned onFixed a couple more unneccessarily visible functions
bib/cite: add UMFPACK
fixes for new PetscOptions.. API that are needed based on problems with nightly build
Explicitly set the function pointer for MatMatSolve to NULL if the external packages does not provide a specific implementation for them
updated manual pages for external direct solvers to explicitly state how to configure PETSc for them and to run with them with KSP
updated PETSc directory layout to match standard packaging strategiesinclude/petsc finclude,private,mpiunilib/petsc confbin/petsc*
Since SuiteSparse uses long for 64 bit indices and PETSc uses long long some compilers warn about non-matching types (even though everything is fine)Add castes to SuiteSparse calls to prevent warnin
Since SuiteSparse uses long for 64 bit indices and PETSc uses long long some compilers warn about non-matching types (even though everything is fine)Add castes to SuiteSparse calls to prevent warningsAlso fix several nightly build output files to prevent noise in testing
suitesparse: fix compile warning with complex build
suitesparse: use (upstream) build defaults - and not change SuiteSparse_long during build (by PETSc).Also remove UF_long usage in code [this was out of sync with UF_long -> SuiteSparse_long change
suitesparse: use (upstream) build defaults - and not change SuiteSparse_long during build (by PETSc).Also remove UF_long usage in code [this was out of sync with UF_long -> SuiteSparse_long change in SuiteSparse.py]Add error message when using 64-bit-indices on 32bit machines (as its not supported by default suitesparse build)
-mat_umfpack_ordering - CHOLMOD, AMD, GIVEN, METIS, BEST, NONE was not documented in manual page!
Added VecLockPush() and VecLockPop() to make vector read onlyUsed VecLockPush() and VecLockPop() in a couple of key locations; PCApply(), KSPSolve(), MatMult()Fixed many uses of VecGetArray() to Ve
Added VecLockPush() and VecLockPop() to make vector read onlyUsed VecLockPush() and VecLockPop() in a couple of key locations; PCApply(), KSPSolve(), MatMult()Fixed many uses of VecGetArray() to VecGetArrayRead()Added VecGet/RestoreArrayPair() for commonly occuring patternAdded const to many locations driven by use of VecGetArrayRead()
Merge branch 'barry/update-suitesparse-version'Conflicts: src/ksp/ksp/examples/tests/makefile
manual merge of conflict
Updated to support SuiteSparse 4.4.1added UMFPACK and CHOLMOD examples to test suiteupdated documentation to better unify klu,umfpack, and cholmodIn response to bitbucket issue 88Did not add CHO
Updated to support SuiteSparse 4.4.1added UMFPACK and CHOLMOD examples to test suiteupdated documentation to better unify klu,umfpack, and cholmodIn response to bitbucket issue 88Did not add CHOLMOD GPU support usage to --download-suitesparse yetReported-by: Sean Farley <sean.michael.farley@gmail.com>
properly extern "C"ing MatSolverPackage registration functions
12345678