[petsc-users] Petsc configuration failure in windows 7 x64

Satish Balay balay at mcs.anl.gov
Thu May 30 15:56:58 CDT 2013


pushed 'balay/bajfact-split' as a start.


$ wc -l baijfact2.c baijsolv.c baijsolvnat.c baijsolvtran.c baijsolvtrannat.c 
   790 baijfact2.c
  1500 baijsolv.c
  1773 baijsolvnat.c
  1383 baijsolvtran.c
   870 baijsolvtrannat.c
  6316 total

$ wc -l *.c | sort -nr
 20612 total
  3640 baij.c
  2140 baij2.c
  1889 baijfact11.c
  1787 baijfact.c
  1773 baijsolvnat.c
  1500 baijsolv.c
  1383 baijsolvtran.c
   870 baijsolvtrannat.c
   790 baijfact2.c
   787 baijfact5.c
   677 baijfact7.c
   608 baijfact9.c
   498 baijfact3.c
   462 baijfact13.c
   441 dgefa2.c
   394 dgefa4.c
   155 dgefa7.c
   151 dgefa6.c
   149 dgefa5.c
   146 dgefa3.c
   104 aijbaij.c
    93 baijfact4.c
    88 dgefa.c
    87 dgedi.c

Satish

On Thu, 30 May 2013, Barry Smith wrote:

> 
> On May 30, 2013, at 1:43 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> > 
> > I see the following routines. I can split them as follows. [Or should
> > I be spliting them up differently?]
> 
>    That is a fine way to start
> 
> > 
> > thanks,
> > Satish
> > 
> > **************** baijfact2.c *******************
> > #define __FUNCT__ "MatILUFactorSymbolic_SeqBAIJ"
> > #define __FUNCT__ "MatILUFactorSymbolic_SeqBAIJ_ilu0"
> > #define __FUNCT__ "MatILUFactorSymbolic_SeqBAIJ_inplace"
> > #define __FUNCT__ "MatLUFactorNumeric_SeqBAIJ_15_NaturalOrdering"
> > #define __FUNCT__ "MatLUFactorNumeric_SeqBAIJ_N"
> > #define __FUNCT__ "MatSetUnfactored_SeqBAIJ_4_NaturalOrdering_SSE"
> > #define __FUNCT__ "MatSetUnfactored_SeqBAIJ_4_NaturalOrdering_SSE_usj"
> > 
> > **************** baijsolv.c *******************
> > 
> > #define __FUNCT__ "MatSolve_SeqBAIJ_1"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_1_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_2"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_2_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_3"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_3_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_Demotion"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_SSE_Demotion"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_5"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_5_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_6"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_6_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_7"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_7_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_N_inplace"
> > 
> > **************** baijsolvnat.c *******************
> > #define __FUNCT__ "MatSolve_SeqBAIJ_15_NaturalOrdering_ver1"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_15_NaturalOrdering_ver2"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_1_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_1_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_2_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_2_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_3_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_3_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_NaturalOrdering_Demotion"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_NaturalOrdering_SSE_Demotion"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_4_NaturalOrdering_SSE_Demotion_usj"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_5_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_5_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_6_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_6_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_7_NaturalOrdering"
> > #define __FUNCT__ "MatSolve_SeqBAIJ_7_NaturalOrdering_inplace"
> > 
> > **************** baijsolvtran.c *******************
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_1"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_1_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_2"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_2_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_3"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_3_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_4"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_4_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_5"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_5_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_6"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_6_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_7"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_7_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_N"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_N_inplace"
> > 
> > **************** baijsolvtrannat.c *******************
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_1_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_1_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_2_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_2_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_3_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_3_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_4_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_4_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_5_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_5_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_6_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_6_NaturalOrdering_inplace"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_7_NaturalOrdering"
> > #define __FUNCT__ "MatSolveTranspose_SeqBAIJ_7_NaturalOrdering_inplace"
> > 
> > 
> > 
> > On Wed, 29 May 2013, Barry Smith wrote:
> > 
> >> 
> >>   Satish,
> >> 
> >>     There appear to be about 70 functions in 6000 lines of code in that file. Please branch off of maint and split it into at least 7 files then test and eventually get it back into maint and master.
> >> 
> >>    Thanks
> >> 
> >>    Barry
> >> 
> >> On May 29, 2013, at 3:38 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> >> 
> >>> Satish Balay <balay at mcs.anl.gov> writes:
> >>> 
> >>>> This piece of code does stress compilers in complex/optimized
> >>>> mode. When I tried previously - I couldn't reproduce the problem [with
> >>>> VS2012]
> >>> 
> >>> We should shorten the file.
> >> 
> >> 
> > 
> 
> 



More information about the petsc-users mailing list