Re: [petsc-dev] Question regarding updating PETSc Fortran examples to embrace post F77 constructs

2016-08-26 Thread Jeff Hammond
If PETSc has symbols greater than 6 characters, it has never been Fortran 77 compliant anyways, so it's a bit strange to ask permission to break it in another way in the examples. Sorry for being a pedant but we've had this debate in the MPI Forum and it is false to conflate punchcard Fortran

[petsc-dev] Are there both a function AND a #define to retrieve PETSc version?

2016-08-26 Thread Eric Chamberland
Hi, wanting to prevent a possible error: I compile and link (dynamically) my code with petsc-3.7.2 BUT I may change my LD_LIBRARY_PATH to point to 3.7.0... I would the like my code to stop and tell me I am using the wrong libs... I could add something like: if (PETSC_VERSION_MAJOR !=

Re: [petsc-dev] VecScatter problem

2016-08-26 Thread Mark Adams
Just an update for the list, Steve seems to have narrowed it down to a compiler bug in the array assignment as Matt suggested. Mark Quick update: just checking ierr isn’t enough to avoid the compiler bug, but adding zero to n1 is. Compiling the code as sent: 145, Loop not fused: function