[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2007-07-08 Thread dfranke at gcc dot gnu dot org
--- Comment #8 from dfranke at gcc dot gnu dot org 2007-07-08 22:41 --- Subject: Bug 28004 Author: dfranke Date: Sun Jul 8 22:41:35 2007 New Revision: 126471 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=126471 Log: gcc: 2007-07-08 Daniel Franke [EMAIL PROTECTED] *

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2007-07-03 Thread dfranke at gcc dot gnu dot org
--- Comment #6 from dfranke at gcc dot gnu dot org 2007-07-03 21:00 --- Mine. -- dfranke at gcc dot gnu dot org changed: What|Removed |Added CC|

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2007-07-03 Thread dfranke at gcc dot gnu dot org
--- Comment #7 from dfranke at gcc dot gnu dot org 2007-07-03 21:06 --- While I got the initially requested warning, ... INTENT(OUT) variables become undefined on subroutine or function entry. We should be able to warn if they are used: ... this seems to generally be the same

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2006-11-11 Thread tkoenig at gcc dot gnu dot org
--- Comment #5 from tkoenig at gcc dot gnu dot org 2006-11-11 11:18 --- Related (and maybe more relevant): INTENT(OUT) variables become undefined on subroutine or function entry. We should be able to warn if they are used: subroutine foo(a,b) real, intent(out) :: a real,

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2006-11-03 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2006-11-03 19:59 --- I think we should issue a warning but not an error, because you can write code that is [...] Note that you should use contains for the code otherwise foo is regarded as real function and the program does not

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2006-11-02 Thread fxcoudert at gcc dot gnu dot org
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2006-11-02 09:47 --- (In reply to comment #1) I presented a patch for this problem and for detected unassigned r-values that was rejected. I don't know what to say; I think that it's a bug, in principle, but the standard does

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2006-06-14 Thread tobias dot burnus at physik dot fu-berlin dot de
--- Comment #2 from tobias dot burnus at physik dot fu-berlin dot de 2006-06-14 09:17 --- Paul, I presented a patch for this problem and for detected unassigned r-values that was rejected. I don't know what to say; I think that it's a bug, in principle, but the standard does not

[Bug fortran/28004] Warn if intent(out) dummy variable is not set

2006-06-13 Thread pault at gcc dot gnu dot org
--- Comment #1 from pault at gcc dot gnu dot org 2006-06-13 19:45 --- Tobias, I presented a patch for this problem and for detected unassigned r-values that was rejected. I don't know what to say; I think that it's a bug, in principle, but the standard does not require it. Paul --