Fix compiler warnings

[ocrickard]

The modernized gfortran compiler has some warnings that it's concerned with:

gfortran -c A1.f
A1.f:939:8:
       A(2)=A(NTOT2+4)
        1
Warning: Array reference at (1) is out of bounds (2 > 1) in dimension 1
A1.f:222:16:
       call RFSN(X,MX,INV,S,IFERR,-2)
                1
Warning: Type mismatch in argument 'a' at (1); passed COMPLEX(4) to REAL(4)
A1.f:236:53:
         call  DRCTSP(NN,MMA, DT, GGT, ID, ZLD(L),NNM,X)
                                                     1
Warning: Type mismatch in argument 'a' at (1); passed COMPLEX(4) to REAL(4)
A1.f:819:19:
       A(NTOT2+4)=A(2)
                   1
Warning: Array reference at (1) is out of bounds (2 > 1) in dimension 1
A1.f:154:17:
       common /EQ/ MFOLD,MA2,TITLE(5),DT, MA , MMA, DF,MX
                 1
Warning: Padding of 2 bytes required before 'dt' in COMMON 'eq' at (1); reorder elements or use -fno-align-commons
gfortran -c B1.f
B1.f:126:17:
       common /EQ/ MFOLD,MA2,TITLE(5),DT, MA , MMA, DF,MX
                 1
Warning: Padding of 2 bytes required before 'dt' in COMMON 'eq' at (1); reorder elements or use -fno-align-commons
B1.f:235:17:
       common /EQ/ MFOLD,MA2,TITLE(5),DT, MA , MMA, DF,MX
                 1
Warning: Padding of 2 bytes required before 'dt' in COMMON 'eq' at (1); reorder elements or use -fno-align-commons
B1.f:290:17:
       common /EQ/ MFOLD,MA2,TITLE(5),DT, MA , MMA, DF,MX
                 1
Warning: Padding of 2 bytes required before 'dt' in COMMON 'eq' at (1); reorder elements or use -fno-align-commons
B1.f:343:17:
       common /EQ/ MFOLD,MA2,TITLE(5),DT, MA , MMA, DF,MX
                 1
Warning: Padding of 2 bytes required before 'dt' in COMMON 'eq' at (1); reorder elements or use -fno-align-commons

B1.f:471:17:
       common /EQ/ MFOLD,MA2,TITLE(5),DT, MA , MMA, DF,MX
                 1
Warning: Padding of 2 bytes required before 'dt' in COMMON 'eq' at (1); reorder elements or use -fno-align-commons
gfortran A1.o B1.o C1.o Main.o -o SHAKE91

Let's get these fixed.

[ocrickard]

@nsitar you may be best qualified to fix these issues.