Revert the function name where it is referenced
Merge branch 'barry/fix-check-ierr-before-freechar/maint' [PR #1220]* barry/fix-check-ierr-before-freechar/maint:Add if (*ierr) return checks for all Fortran stubs that utilize FREECHAR()Otherwis
Merge branch 'barry/fix-check-ierr-before-freechar/maint' [PR #1220]* barry/fix-check-ierr-before-freechar/maint:Add if (*ierr) return checks for all Fortran stubs that utilize FREECHAR()Otherwise the ierr is overwritten by the FREECHAR() thus returning a zero error code when it should not
show more ...
Add if (*ierr) return checks for all Fortran stubs that utilize FREECHAR()Otherwise the ierr is overwritten by the FREECHAR() thus returning a zero error code when it should notCommit-type: bug-f
Add if (*ierr) return checks for all Fortran stubs that utilize FREECHAR()Otherwise the ierr is overwritten by the FREECHAR() thus returning a zero error code when it should notCommit-type: bug-fixReported-by: Tim Steinhoff <kandanovian@gmail.com>
Changed VecScatterCreate() to take a communicator and return scatter as other first class PETSc objects do.Changed old VecScatterCreate() to VecScatterCreateWithData()Completed basic refactorizati
Changed VecScatterCreate() to take a communicator and return scatter as other first class PETSc objects do.Changed old VecScatterCreate() to VecScatterCreateWithData()Completed basic refactorization of VecScatter code, ready for new implementations to be added.(There is still some code duplication between the VecScatter MPI1 and MPI3 code but it can be fixed at anytime without requiring changes to the VecScatter API.Part 5 of a refactorization of VecScatter to be treated as a first class PETSc objectCommit-type: style-fix
fixed memory leak
Minor cleanup, remove some outdated code, remove unneeded constructs, improve manual pages slightly, add missing test caseTime: 2.5 hours
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>
Refactored ./configures handling of package requirements for precision. Now each package indicateswhat it supports withself.precisions = ['single','double','__float128']Updated the package files t
Refactored ./configures handling of package requirements for precision. Now each package indicateswhat it supports withself.precisions = ['single','double','__float128']Updated the package files to indicate what they supportRemoved unneeded #requires arguments from makefiles for external packages.Time: 2 hoursReported-by: Patrick Sanan <patrick.sanan@gmail.com>
Update zfftf.cFortran wrapper with "*comm" is not working. After changing to "MPI_Comm_f2c(*(MPI_Fint*)&*comm)" the function works fine.
some uses of PetscTryMethod() actually require that theobject is correct and the function returns an appropriate value.Change those calls to PetscUseMethod().
Fix reuse of plans for real vectors.For real builds we have to use the *r2c anc *c2r versions of thefftw_execute_dft API.
updated PETSc directory layout to match standard packaging strategiesinclude/petsc finclude,private,mpiunilib/petsc confbin/petsc*
FFTW: Updated for vector locking
manual merge of conflict
convert some PetscMalloc() to PetscMalloc1()remove unneeded () in first argument to PetscMalloc/Calloc1()fixes for MATLAB examples
MatGetVecs() and KSPGetVecs() replaced with MatCreateVecs() and KSPCreateVecs()since they are creators not getters
Mat: Fix Fortran wrapper for MatCreateFFT()
take out petsc/fftw interface support for DIM>=3 of r2c/c2r until the buggy code is fixed.
rm unused variables; cast (int*)ndim for real 64-bit build
cleanup tests for FFTW
add fftw_plan_guru64_dft(): works for sequential complex cases
small fix for real build; update fftw.py
bugfix for 64-bit, complex build
use fftw_plan_guru_dft() for complex and 64-bit build
rm unused variable; -mat_fftw_plannerflags FFTW_MEASURE gives incorrect results for ndim=3 and 4, complex build
12345678