Re: [petsc-maint] Bug#897006: petsc FTBFS on mips: f951: out of memory

On Sat, 2018-04-28 at 18:11 +0300, Adrian Bunk wrote:
> 
> The failing command is:
> mpif90 -c -g -O2 -fstack-protector-strong -fPIC   -Wdate-time
> -D_FORTIFY_SOURCE=2 -fdebug-prefix-map=/home/bunk/build/petsc-
> 3.9.0+dfsg1=. -I/home/bunk/build/petsc-3.9.0+dfsg1/include
> -I/home/bunk/build/petsc-3.9.0+dfsg1/mips-linux-gnu-real-
> debug/include -I/usr/include/suitesparse -I/usr/include/superlu
> -I/usr/include/superlu-dist -I/usr/include/hypre
> -I/usr/include/hdf5/serial -I/usr/include/scotch  -Wdate-time
> -D_FORTIFY_SOURCE=2  -MMD -MP /home/bunk/build/petsc-
> 3.9.0+dfsg1/src/dm/f90-mod/petscdmmod.F -o mips-linux-gnu-real-
> debug/obj/dm/f90-mod/petscdmmod.o -J/home/bunk/build/petsc-
> 3.9.0+dfsg1/mips-linux-gnu-real-debug/include
> 
> I am hitting the 2 GB limit even after changing to -g0 -O0.

Would it work to split petscdmmod.F into two pieces, e.g. one with
petscdmda and central petscdm and the other with petscdmplex? 

Naively the two separate object files would then need around 1GB,
allowing mpif90 -c to succeed.  This assumes that linking won't emit
the same problem.

Drew