[Octopus-devel] INTENT(OUT) variable not set
Tobias Burnus
tobias.burnus at physik.fu-berlin.de
Mon Jul 9 09:30:26 WEST 2007
Hi,
gfortran complains that not all INTENT(OUT) variables have been set. I
did not check whether they should be set to INTENT(INOUT), but I know at
least one compiler which returns an uninitialized variable if not set in
the procedure, even if the argument was initialized before the call.
pfft3d.F90:850.59:
subroutine kernelfft(n1,n2,n3,nd1,nd2,nd3,nproc,iproc,zf,zr,comm)
1
Warning: dummy argument 'zr' at (1) was declared INTENT(OUT) but was not
set
td_rti.F90:716.34:
subroutine td_zopt(xre, xim, yre, yim)
1
Warning: dummy argument 'yre' at (1) was declared INTENT(OUT) but was
not set
td_rti.F90:716.39:
subroutine td_zopt(xre, xim, yre, yim)
1
Warning: dummy argument 'yim' at (1) was declared INTENT(OUT) but was
not set
td_rti.F90:695.33:
subroutine td_zop(xre, xim, yre, yim)
1
Warning: dummy argument 'yre' at (1) was declared INTENT(OUT) but was
not set
td_rti.F90:695.38:
subroutine td_zop(xre, xim, yre, yim)
1
Warning: dummy argument 'yim' at (1) was declared INTENT(OUT) but was
not set
* * *
Some compilers create nonesense in this case:
curv_gygi.F90:144.39:
call droot_solver_run(rs, getf, x, conv, startval = x)
1
Warning: Same effective argument connected with INTENT(OUT) argument
"root" und INTENT(IN) argument "startval" at (1)
td_write.F90:212.58:
call loct_parse_int(check_inp('TDProjStateStart'),
w%gs_st%st_start, w%
1
Warning: Same effective argument connected with INTENT(OUT) argument
"def" und INTENT(IN) argument "res" at (1)
Tobias
More information about the Octopus-devel
mailing list