April 2016 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] gfortran -Wno-unused-variable
by Satish Balay 10 Apr '16

10 Apr '16

changed in balay/fix-fortran-unused_variables and merged to next. Satish On Sun, 10 Apr 2016, Satish Balay wrote: > The change was done long ago.. I don't remember the reason [and it > wasn't documented in the commit message :(] > > https://bitbucket.org/petsc/petsc/commits/aa4d2986619717de6f4da384f5fcafb39… > > Perhaps we should revert it. > > I see a bunch of warnings with petsc fortran includes/examples. Will > fix and push.. > > Satish > > On Sun, 10 Apr 2016, Lisandro Dalcin wrote: > > > Why is this warning silenced? Why should we treat Fortran different > > than C/C++ regarding unused variables? Maybe some old gfortran > > confused local variables with dummy arguments? > > > > > > > >

1 0

Re: [petsc-dev] gfortran -Wno-unused-variable
by Satish Balay 10 Apr '16

10 Apr '16

The change was done long ago.. I don't remember the reason [and it wasn't documented in the commit message :(] https://bitbucket.org/petsc/petsc/commits/aa4d2986619717de6f4da384f5fcafb39… Perhaps we should revert it. I see a bunch of warnings with petsc fortran includes/examples. Will fix and push.. Satish On Sun, 10 Apr 2016, Lisandro Dalcin wrote: > Why is this warning silenced? Why should we treat Fortran different > than C/C++ regarding unused variables? Maybe some old gfortran > confused local variables with dummy arguments? > > >

1 0

gfortran -Wno-unused-variable
by Lisandro Dalcin 10 Apr '16

10 Apr '16

Why is this warning silenced? Why should we treat Fortran different than C/C++ regarding unused variables? Maybe some old gfortran confused local variables with dummy arguments? -- Lisandro Dalcin ============ Research Scientist Computer, Electrical and Mathematical Sciences & Engineering (CEMSE) Extreme Computing Research Center (ECRC) King Abdullah University of Science and Technology (KAUST) http://ecrc.kaust.edu.sa/ 4700 King Abdullah University of Science and Technology al-Khawarizmi Bldg (Bldg 1), Office # 4332 Thuwal 23955-6900, Kingdom of Saudi Arabia http://www.kaust.edu.sa Office Phone: +966 12 808-0459

1 0

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-04-08
by Barry Smith 08 Apr '16

08 Apr '16

Toby, We'll be filtering out these false positives. It is just taking us a couple of days to determine that needs to be filtered. Barry > On Apr 8, 2016, at 2:36 PM, Tobin Isaac <tisaac(a)uchicago.edu> wrote: > > > I spent a couple minutes verifying that there is no code path where > that variable is not initialized on line 3437. > > -Wmaybe-uninitialized seems to generate a lot of false positives. > Coupled with the blame digest's poor ability to assign blame, this > proactive approach seems to waste more time than a reactive > SEGV->valgrind->fix approach. > > Cheers, > Toby > > On Fri, Apr 08, 2016 at 02:12:22PM -0500, Satish Balay wrote: >> This should have been sent to Toby. >> >> I don't really understand the issue here. Its triggered by --with-debugging=0. I'm >> not sure why these compilers are pointing to petscsys.h. I get slightly different message >> on my laptop. >> >> mpicc -c -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fvisibility=hidden -g -O -I/home/balay/petsc/include -I/home/balay/petsc/arch-linux2-c-opt/include -I/home/balay/soft/mpich-3.1.4/include -MMD -MP /home/balay/petsc/src/dm/impls/plex/plextree.c -o arch-linux2-c-opt/obj/src/dm/impls/plex/plextree.o >> /home/balay/petsc/src/dm/impls/plex/plextree.c: In function ‘DMPlexComputeInjectorTree’: >> /home/balay/petsc/src/dm/impls/plex/plextree.c:3484:11: warning: ‘childrenMats’ may be used uninitialized in this function [-Wmaybe-uninitialized] >> ierr = PetscFree(refPointFieldMats);CHKERRQ(ierr); >> ^ >> /home/balay/petsc/src/dm/impls/plex/plextree.c:3507:18: note: ‘childrenMats’ was declared here >> PetscScalar ***childrenMats; >> ^ >> >> Satish >> >> On Fri, 8 Apr 2016, PETSc checkBuilds wrote: >> >>> >>> >>> Dear PETSc developer, >>> >>> This email contains listings of contributions attributed to you by >>> `git blame` that caused compiler errors or warnings in PETSc automated >>> testing. Follow the links to see the full log files. Please attempt to fix >>> the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable >>> to resolve the issues. >>> >>> Thanks, >>> The PETSc development team >>> >>> ---- >>> >>> warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/49d7da5 >>> PetscMalloc: allow ptr=malloc(0) and free(ptr) >>> >>> include/petscsys.h:1157 >>> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >>> /usr/home/balay/petsc.clone-2/include/petscsys.h:1157:88: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] >>> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >>> /sandbox/petsc/petsc.clone-3/include/petscsys.h:1157:88: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] >>> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >>> /usr/home/balay/petsc.clone/include/petscsys.h:1157:39: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] >>> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >>> /sandbox/petsc/petsc.clone-4/include/petscsys.h:1157:25: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] >>> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >>> /sandbox/petsc/petsc.clone/include/petscsys.h:1157:25: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] >>> >>> ---- >>> To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov. >>> >

1 0

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-04-08
by Tobin Isaac 08 Apr '16

08 Apr '16

I spent a couple minutes verifying that there is no code path where that variable is not initialized on line 3437. -Wmaybe-uninitialized seems to generate a lot of false positives. Coupled with the blame digest's poor ability to assign blame, this proactive approach seems to waste more time than a reactive SEGV->valgrind->fix approach. Cheers, Toby On Fri, Apr 08, 2016 at 02:12:22PM -0500, Satish Balay wrote: > This should have been sent to Toby. > > I don't really understand the issue here. Its triggered by --with-debugging=0. I'm > not sure why these compilers are pointing to petscsys.h. I get slightly different message > on my laptop. > > mpicc -c -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fvisibility=hidden -g -O -I/home/balay/petsc/include -I/home/balay/petsc/arch-linux2-c-opt/include -I/home/balay/soft/mpich-3.1.4/include -MMD -MP /home/balay/petsc/src/dm/impls/plex/plextree.c -o arch-linux2-c-opt/obj/src/dm/impls/plex/plextree.o > /home/balay/petsc/src/dm/impls/plex/plextree.c: In function ‘DMPlexComputeInjectorTree’: > /home/balay/petsc/src/dm/impls/plex/plextree.c:3484:11: warning: ‘childrenMats’ may be used uninitialized in this function [-Wmaybe-uninitialized] > ierr = PetscFree(refPointFieldMats);CHKERRQ(ierr); > ^ > /home/balay/petsc/src/dm/impls/plex/plextree.c:3507:18: note: ‘childrenMats’ was declared here > PetscScalar ***childrenMats; > ^ > > Satish > > On Fri, 8 Apr 2016, PETSc checkBuilds wrote: > > > > > > > Dear PETSc developer, > > > > This email contains listings of contributions attributed to you by > > `git blame` that caused compiler errors or warnings in PETSc automated > > testing. Follow the links to see the full log files. Please attempt to fix > > the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable > > to resolve the issues. > > > > Thanks, > > The PETSc development team > > > > ---- > > > > warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/49d7da5 > > PetscMalloc: allow ptr=malloc(0) and free(ptr) > > > > include/petscsys.h:1157 > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /usr/home/balay/petsc.clone-2/include/petscsys.h:1157:88: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /sandbox/petsc/petsc.clone-3/include/petscsys.h:1157:88: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /usr/home/balay/petsc.clone/include/petscsys.h:1157:39: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /sandbox/petsc/petsc.clone-4/include/petscsys.h:1157:25: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /sandbox/petsc/petsc.clone/include/petscsys.h:1157:25: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > > > > ---- > > To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov. > >

1 0

Re: [petsc-dev] Need help with Fortran code/compiler issue
by Barry Smith 08 Apr '16

08 Apr '16

Thanks, I've done it. > On Apr 8, 2016, at 3:23 AM, Lawrence Mitchell <lawrence.mitchell(a)imperial.ac.uk> wrote: > >> >> On 7 Apr 2016, at 19:46, Barry Smith <bsmith(a)mcs.anl.gov> wrote: >> >> >> src/sys/classes/bag/f2003-src/fsrc/bagenum.F has the code fragment >> >> Subroutine PetscBagRegisterEnum(bag,addr,FArray,def,n,h,ierr) >> use,intrinsic :: iso_c_binding >> implicit none >> >> PetscBag bag >> character(*) n,h >> character(*) FArray(*) >> PetscEnum :: def >> PetscErrorCode,intent(out) :: ierr >> PetscReal addr(*) >> >> Type(C_Ptr),Dimension(:),Pointer :: CArray >> character(kind=c_char),pointer :: nullc => null() >> PetscInt :: i,Len >> Character(kind=C_char,len=256),Dimension(:),Pointer::list1 >> >> do i=1,256 >> if (len_trim(Farray(i)) .eq. 0) then >> Len = i-1 >> goto 100 >> endif >> if (len_trim(Farray(i)) .gt. 255) then >> ierr = PETSC_ERR_ARG_OUTOFRANGE >> return >> endif >> enddo >> ierr = PETSC_ERR_ARG_OUTOFRANGE >> return >> >> 100 continue >> >> Allocate(list1(Len),stat=ierr); >> Allocate(CArray(Len+1),stat=ierr) >> do i=1,Len >> list1(i) = trim(FArray(i))//C_NULL_CHAR >> enddo >> >> CArray = (/(c_loc(list1(i)),i=1,Len),c_loc(nullc)/) >> call PetscBagRegisterEnumPrivate(bag,addr,CArray,def,n,h,ierr) >> DeAllocate(CArray) >> DeAllocate(list1) >> End Subroutine >> >> which produces the following warning with one Fortran compiler: >> >> /Users/petsc/petsc.clone-4/src/sys/objects/f2003-src/fsrc/optionenum.F:35:0: >> >> CArray = (/(c_loc(list1(i)),i=1,Len),c_loc(nullc)/) >> ^ >> Warning: 'list1.data' may be used uninitialized in this function [-Wmaybe-uninitialized] >> >> Do any Fortran programmers know if the code is correct or if this is an incorrect warning from the compiler? > > > This is occurring because the return value from allocate(list1(Len),stat=ierr) is not being checked and so list1 may be NULL later on. > > This squashes the warning for me: > > Allocate(list1(Len),stat=ierr) > if (ierr .ne. 0) then > ierr = PETSC_ERR_MEM > return > endif > > One should presumably do the same after the allocation of CArray as well. > > It looks like the same change would apply in optionenum.F > Cheers, > > Lawrence

1 0

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-04-08
by Satish Balay 08 Apr '16

08 Apr '16

This should have been sent to Toby. I don't really understand the issue here. Its triggered by --with-debugging=0. I'm not sure why these compilers are pointing to petscsys.h. I get slightly different message on my laptop. mpicc -c -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fvisibility=hidden -g -O -I/home/balay/petsc/include -I/home/balay/petsc/arch-linux2-c-opt/include -I/home/balay/soft/mpich-3.1.4/include -MMD -MP /home/balay/petsc/src/dm/impls/plex/plextree.c -o arch-linux2-c-opt/obj/src/dm/impls/plex/plextree.o /home/balay/petsc/src/dm/impls/plex/plextree.c: In function οΏ½DMPlexComputeInjectorTreeοΏ½: /home/balay/petsc/src/dm/impls/plex/plextree.c:3484:11: warning: οΏ½childrenMatsοΏ½ may be used uninitialized in this function [-Wmaybe-uninitialized] ierr = PetscFree(refPointFieldMats);CHKERRQ(ierr); ^ /home/balay/petsc/src/dm/impls/plex/plextree.c:3507:18: note: οΏ½childrenMatsοΏ½ was declared here PetscScalar ***childrenMats; ^ Satish On Fri, 8 Apr 2016, PETSc checkBuilds wrote: > > > Dear PETSc developer, > > This email contains listings of contributions attributed to you by > `git blame` that caused compiler errors or warnings in PETSc automated > testing. Follow the links to see the full log files. Please attempt to fix > the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable > to resolve the issues. > > Thanks, > The PETSc development team > > ---- > > warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/49d7da5 > PetscMalloc: allow ptr=malloc(0) and free(ptr) > > include/petscsys.h:1157 > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /usr/home/balay/petsc.clone-2/include/petscsys.h:1157:88: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /sandbox/petsc/petsc.clone-3/include/petscsys.h:1157:88: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /usr/home/balay/petsc.clone/include/petscsys.h:1157:39: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /sandbox/petsc/petsc.clone-4/include/petscsys.h:1157:25: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /sandbox/petsc/petsc.clone/include/petscsys.h:1157:25: warning: 'childrenMats' may be used uninitialized in this function [-Wmaybe-uninitialized] > > ---- > To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov. >

1 0

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-04-08
by Barry Smith 08 Apr '16

08 Apr '16

huh, I don't see your changes being relevant. I don't think you should push them. > On Apr 8, 2016, at 11:39 AM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > [Checking this for Emil] > > Its not clear why this warning is coming up. The following fixes > it. (not sure if its a workarround or a fix) > > Any objections to pushing? > > thanks, > Statish > ------------- > diff --git a/src/ts/impls/explicit/rk/rk.c b/src/ts/impls/explicit/rk/rk.c > index e3d106f..dfe3de9 100644 > --- a/src/ts/impls/explicit/rk/rk.c > +++ b/src/ts/impls/explicit/rk/rk.c > @@ -566,7 +566,6 @@ static PetscErrorCode TSAdjointStep_RK(TS ts) > PetscFunctionBegin; > t = ts->ptime; > rk->status = TS_STEP_INCOMPLETE; > - h = ts->time_step; > ierr = TSPreStep(ts);CHKERRQ(ierr); > for (i=s-1; i>=0; i--) { > rk->stage_time = t + h*(1.0-c[i]); > @@ -772,6 +771,7 @@ static PetscErrorCode TSSetUp_RK(TS ts) > } > if (!rk->tableau) { > ierr = TSRKSetType(ts,TSRKDefault);CHKERRQ(ierr); > + rk = (TS_RK*)ts->data; > } > tab = rk->tableau; > s = tab->s; > @@ -937,6 +937,7 @@ PetscErrorCode TSRKGetType_RK(TS ts,TSRKType *rktype) > PetscFunctionBegin; > if (!rk->tableau) { > ierr = TSRKSetType(ts,TSRKDefault);CHKERRQ(ierr); > + rk = (TS_RK*)ts->data; > } > *rktype = rk->tableau->name; > PetscFunctionReturn(0); > > > On Fri, 8 Apr 2016, PETSc checkBuilds wrote: > >> >> >> Dear PETSc developer, >> >> This email contains listings of contributions attributed to you by >> `git blame` that caused compiler errors or warnings in PETSc automated >> testing. Follow the links to see the full log files. Please attempt to fix >> the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable >> to resolve the issues. >> >> Thanks, >> The PETSc development team >> >> ---- >> >> warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/f68a32c >> Implemented the renovated RK. >> >> src/ts/impls/explicit/rk/rk.c:775 >> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >> /sandbox/petsc/petsc.clone/src/ts/impls/explicit/rk/rk.c:775:10: warning: Access to field 's' results in a dereference of a null pointer (loaded from variable 'tab') >> >> src/ts/impls/explicit/rk/rk.c:939 >> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] >> /sandbox/petsc/petsc.clone/src/ts/impls/explicit/rk/rk.c:939:13: warning: Access to field 'name' results in a dereference of a null pointer (loaded from field 'tableau') >> >> ---- >> To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov. >> >

1 0

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-04-08
by Satish Balay 08 Apr '16

08 Apr '16

I can confirm the 'analyzer' warnings are fixed in thi branch. Satish On Fri, 8 Apr 2016, Michael Lange wrote: > Hi Matt, > > I just pushed the branch mlange/fix-plex-fluent-reader that re-enables the > plex-fluent test cases and hopefully fixes these warnings. Can you please > double-check this and merge to next/master? > > Thanks, > Michael > > On 08/04/16 15:00, PETSc checkBuilds wrote: > > > > Dear PETSc developer, > > > > This email contains listings of contributions attributed to you by > > `git blame` that caused compiler errors or warnings in PETSc automated > > testing. Follow the links to see the full log files. Please attempt to fix > > the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are > > unable > > to resolve the issues. > > > > Thanks, > > The PETSc development team > > > > ---- > > > > warnings attributed to commit > > https://bitbucket.org/petsc/petsc/commits/3f6dc66 > > Plex-Fluent: Add coordinates to the generated Plex > > > > src/dm/impls/plex/plexfluent.c:408 > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /sandbox/petsc/petsc.clone/src/dm/impls/plex/plexfluent.c:408:27: > > warning: Array access (from variable 'coordsIn') results in a null > > pointer dereference > > > > ---- > > > > warnings attributed to commit > > https://bitbucket.org/petsc/petsc/commits/f732056 > > Plex-Fluent: Build Plex topology from face connectivity > > > > src/dm/impls/plex/plexfluent.c:322 > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > > /sandbox/petsc/petsc.clone/src/dm/impls/plex/plexfluent.c:322:27: > > warning: Array access (from variable 'faces') results in a null > > pointer dereference > > > > ---- > > To opt-out from receiving these messages - send a request to > > petsc-dev(a)mcs.anl.gov. > >

1 0

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-04-08
by Satish Balay 08 Apr '16

08 Apr '16

[Checking this for Emil] Its not clear why this warning is coming up. The following fixes it. (not sure if its a workarround or a fix) Any objections to pushing? thanks, Statish ------------- diff --git a/src/ts/impls/explicit/rk/rk.c b/src/ts/impls/explicit/rk/rk.c index e3d106f..dfe3de9 100644 --- a/src/ts/impls/explicit/rk/rk.c +++ b/src/ts/impls/explicit/rk/rk.c @@ -566,7 +566,6 @@ static PetscErrorCode TSAdjointStep_RK(TS ts) PetscFunctionBegin; t = ts->ptime; rk->status = TS_STEP_INCOMPLETE; - h = ts->time_step; ierr = TSPreStep(ts);CHKERRQ(ierr); for (i=s-1; i>=0; i--) { rk->stage_time = t + h*(1.0-c[i]); @@ -772,6 +771,7 @@ static PetscErrorCode TSSetUp_RK(TS ts) } if (!rk->tableau) { ierr = TSRKSetType(ts,TSRKDefault);CHKERRQ(ierr); + rk = (TS_RK*)ts->data; } tab = rk->tableau; s = tab->s; @@ -937,6 +937,7 @@ PetscErrorCode TSRKGetType_RK(TS ts,TSRKType *rktype) PetscFunctionBegin; if (!rk->tableau) { ierr = TSRKSetType(ts,TSRKDefault);CHKERRQ(ierr); + rk = (TS_RK*)ts->data; } *rktype = rk->tableau->name; PetscFunctionReturn(0); On Fri, 8 Apr 2016, PETSc checkBuilds wrote: > > > Dear PETSc developer, > > This email contains listings of contributions attributed to you by > `git blame` that caused compiler errors or warnings in PETSc automated > testing. Follow the links to see the full log files. Please attempt to fix > the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable > to resolve the issues. > > Thanks, > The PETSc development team > > ---- > > warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/f68a32c > Implemented the renovated RK. > > src/ts/impls/explicit/rk/rk.c:775 > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /sandbox/petsc/petsc.clone/src/ts/impls/explicit/rk/rk.c:775:10: warning: Access to field 's' results in a dereference of a null pointer (loaded from variable 'tab') > > src/ts/impls/explicit/rk/rk.c:939 > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/08/build_next_…] > /sandbox/petsc/petsc.clone/src/ts/impls/explicit/rk/rk.c:939:13: warning: Access to field 'name' results in a dereference of a null pointer (loaded from field 'tableau') > > ---- > To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov. >

1 0