PC[ASM|BJACOBI|GASM]: propagate prefix from parent
Convert MPI error type to PETSc error with string message for all MPI callsNow PETSc examples will ONLY return PETSc error codes and never MPI error codes directly so we can understand and post-pro
Convert MPI error type to PETSc error with string message for all MPI callsNow PETSc examples will ONLY return PETSc error codes and never MPI error codes directly so we can understand and post-process their errors better.The test harness will now automatically retry tests that fail with MPI, this may help with Intel MPI that produces seemingly random failures.Commit-type: error-checking/spend 30m
show more ...
Add support to Fortran interface for PCASMGetSubKSP() and PCGASMGetSubKSP() to use PETSC_NULL_INT for first two argumentsCommit-type: feature/spend 15mReported-by: Nathan Wukie
Fix bug introduced by PCASMSetSubMatType() when MAT_REUSE_MATRIX is used with a different type of pmat compared to pmat[i]Always destroy previously created pmat[i] and use MAT_INITIAL_MATRIXissue
Fix bug introduced by PCASMSetSubMatType() when MAT_REUSE_MATRIX is used with a different type of pmat compared to pmat[i]Always destroy previously created pmat[i] and use MAT_INITIAL_MATRIXissue #788[0]PETSC ERROR: #1 PetscMemcmp() line 40 in /Users/vtdb72/Documents/work/src/deps/petsc/src/sys/utils/memc.c[0]PETSC ERROR: #2 MatCreateSubMatrix_SeqAIJ() line 2635 in /Users/vtdb72/Documents/work/src/deps/petsc/src/mat/impls/aij/seq/aij.c[0]PETSC ERROR: #3 MatCreateSubMatrices_SeqAIJ() line 2881 in /Users/vtdb72/Documents/work/src/deps/petsc/src/mat/impls/aij/seq/aij.c[0]PETSC ERROR: #4 MatCreateSubMatrices() line 6857 in /Users/vtdb72/Documents/work/src/deps/petsc/src/mat/interface/matrix.c...Commit-type: bug-fix/spend 45mReported-by: Lawrence Mitchell https://gitlab.com/wence
PCASM: fix for KOKKOS/CUDA
PCASMGetSubKSP, PCGASMGetSubKSP: add fortran interface definitionsFixes pflotran+gfortran-10 build.
Fix some %d that should be %DFix some source code styleCommit-type: style-fix/spend 15m
Turn on checkbadSource test to generate an error when found; fix all source code that causes errorsCommit-type: portability-fix, testing-fix, style-fix, feature, maintainability/spend 1.5h
PCASM + PCGASM + PCSPAI: add PCMatApply()
Updated the use of sizeof() when possible instead of using hardwired sizes for functions whose string argumentsneed sizes. In particular done for PetscOptionsGetString(), PetscOptionsString(), and a
Updated the use of sizeof() when possible instead of using hardwired sizes for functions whose string argumentsneed sizes. In particular done for PetscOptionsGetString(), PetscOptionsString(), and a few other utilitiesCommit-type: style-fixDevelopment Tools: Vim, Emacs, Eclipse
KSP/PC: Fix 0 ->NULL for pointers
Merge remote-tracking branch 'origin/maint'
Merge remote-tracking branch 'origin/jolivet/fix-symlink-free' into maint
Minor fixes and improvements* Typos* MatMatSolve() improvements* MatDense[Get|Restore]ColumnF90()* MatKAIJGetScaledIdentity()
Single petscdir.mk
PC: ASM, Block Jacobi: when viewing, note local solver on rank 0 is shownThe KSPView() call shows the (sub-)KSP on rank 0, which should have the sametype, PC, parameters, etc., but will not be the
PC: ASM, Block Jacobi: when viewing, note local solver on rank 0 is shownThe KSPView() call shows the (sub-)KSP on rank 0, which should have the sametype, PC, parameters, etc., but will not be the identical solver,as the size of the local subdomains and the entries of the localsubmatrices will be different. For instance, the output only showsthe local Mat for rank 0, which might confuse a user into thinking thatthe subdomains are all of the same size when they are not. Similarly,a PC like LU would show different factorization details on differentranks, even though the solver settings are the same.Make the viewer output more precise by noting explicitly that isdisplaying information for the rank 0 subsolver.Update test output with the new string.
build: add more support for not needing to set PETSC_DIR yet build with PETSc, also support for GNU make to directly use "make test" instead of "make -f gmakefile.test"Still needs -include ../petsc
build: add more support for not needing to set PETSC_DIR yet build with PETSc, also support for GNU make to directly use "make test" instead of "make -f gmakefile.test"Still needs -include ../petscdir.mk in many of the makefilesStill needs the link for ../petscdir.mk in many directoriesGNUMakefile: call legacy makefile recursively instead of including itGNUMakefile: promote default "all" target; "libs" builds libpetsc*GNUMakefile: If gnumake < 4.2 prefer makefile wrapper interface over direct gmakefile interface to avoid the following warningsgmakefile.test:92: arch-ci-linux-cxx-cmplx-pkgs-64idx/tests/testfiles: No such file or directorygmakefile:67: arch-ci-linux-cxx-cmplx-pkgs-64idx/lib/petsc/conf/files: No such file or directoryCommit-type: testing-fix, feature, usabilityThanks-to: Jed Brown jed@jedbrown.org
Remove usage of PETSC_HAVE_FORTRAN_STDCALL, PETSC_BLASLAPACK_STDCALL, HAVE_FORTRAN_MIXED_STR_ARG flags - as Compaq f90 compiler is no longer supported
Missing manual page
Do not default to BASIC for ASM preconditioner, it can require signifigently more iterations (and time)Commit-type: optimizationReported-by: Pierre Jolivet <pierre.jolivet@enseeiht.fr>
More typos
Some typos.
Fix a bunch of PetscValidPointer() -> PetscValidXXXPointer()
No more batch submission script; this is all due to a very smart idea of Lisandro Dalcin*) removed or fixed all remaining --know-xx options that required a batch submission script*) removed all de
No more batch submission script; this is all due to a very smart idea of Lisandro Dalcin*) removed or fixed all remaining --know-xx options that required a batch submission script*) removed all details of --known-size-- that are no longer needed*) cleaned up BAIJMKL source code, made it work with the rest of PETSc and removed is dependence on a batch submission script, added test case for BAIJMKL*) update the installation guide on batsch submissions and OpenMP*) print MKL version, print OpenMP usage with mkl_sparse optionsCommit-type: bug-fix, portability-fix, style-fix, feature, documentation, exampleThanks-to: Lisandro Dalcin <dalcinl@gmail.com>$ ./configure --with-batch=============================================================================== Configuring PETSc to compile on your system============================================================================================================================================================== ***** WARNING: Cannot determine if MPI_INT64_T works on your system in batch-mode! Assuming it does work. Run with --known-mpi-int64_t=0 if you know it does not work (very unlikely). Run with --known-mpi-int64_t=1 to remove this warning message. warning message ***** =============================================================================== =============================================================================== ***** WARNING: Cannot determine if MPI_C_DOUBLE_COMPLEX works on your system in batch-mode! Assuming it does work. Run with --known-mpi-c-double-complex=0 if you know it does not work (very unlikely). Run with --known-mpi-c-double-complex=1 to remove this warning message. warning message ***** =============================================================================== =============================================================================== ***** WARNING: Cannot verify that MPI is a shared library - in batch-mode! If MPI is a static library but linked into multiple shared libraries that the application uses, sometimes compiles work - but one might get run-time errors. If you know that the MPI library is shared - run with --known-mpi-shared-libraries=1 option to remove this warning message ***** =============================================================================== =============================================================================== ***** WARNING: Cannot determine if BLAS/LAPACK uses 32 bit or 64 bit integers in batch-mode! Assuming 32 bit integers. Run with --known-64-bit-blas-indices if you know they are 64 bit. Run with --known-64-bit-blas-indices=0 to remove this warning message. warning message ***** ===============================================================================
12345678910>>...14