Use PetscObjectReferenceWrapper to handle different PETSC versions

Author: Ben Fulton

assemble/Full_Projection.F90

@@ -425,8 +425,7 @@ subroutine petsc_solve_setup_full_projection(y,A,b,ksp,petsc_numbering_p,name,so
         call MatSchurComplementGetKSP(A,ksp_schur,ierr)
 
         ! we keep our own reference, so it can be re-used in the velocity correction solve
-      !   call PetscObjectReferenceWrapper(ksp_schur, ierr)
-        call PetscObjectReference(ksp_schur, ierr)
+        call PetscObjectReferenceWrapper(ksp_schur, ierr)
         inner_M%ksp = ksp_schur
       else
         ! we have a ksp (presumably from the first velocity solve), try to reuse it

femtools/Solvers.F90

@@ -983,8 +983,7 @@ subroutine petsc_solve_setup(y, A, b, ksp, petsc_numbering, &
       ksp_pointer = ksp
 
       ! make sure we don't destroy it, the %ksp becomes a separate reference
-      ! call PetscObjectReferenceWrapper(ksp, ierr)
-      call PetscObjectReference(ksp, ierr)
+      call PetscObjectReferenceWrapper(ksp, ierr)
     else
       ! matrices coming from block() can't cache
       FLAbort("User wants to cache solver context, but no proper matrix is provided.")
@@ -994,14 +993,12 @@ subroutine petsc_solve_setup(y, A, b, ksp, petsc_numbering, &
 
     ! ksp is a copy of matrix%ksp, make it a separate reference,
     ! so we can KSPDestroy it without destroying matrix%ksp
-    ! call PetscObjectReferenceWrapper(ksp, ierr)
-    call PetscObjectReference(ksp, ierr)
+    call PetscObjectReferenceWrapper(ksp, ierr)
 
     ! same for the matrix, kspgetoperators returns the matrix reference
     ! owned by the ksp - make it a separate reference
-    ! call PetscObjectReferenceWrapper(A, ierr)
-    call PetscObjectReference(ksp, ierr)
-
+    call PetscObjectReferenceWrapper(A, ierr)
+    
   end if
 
   b=PetscNumberingCreateVec(petsc_numbering)