[Bug fortran/25061] procedure name conflict

2007-06-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-06-21 02:11 --- Fixed on 4.3, closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/25061] procedure name conflict

2007-06-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-06-21 01:48 --- Subject: Bug 25061 Author: jvdelisle Date: Thu Jun 21 01:48:21 2007 New Revision: 125907 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=125907 Log: 2007-06-20 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/25061] procedure name conflict

2007-06-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-06-21 01:18 --- Subject: Bug 25061 Author: jvdelisle Date: Thu Jun 21 01:18:02 2007 New Revision: 125906 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=125906 Log: 2007-06-20 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/25061] procedure name conflict

2007-06-18 Thread patchapp at dberlin dot org
--- Comment #3 from patchapp at dberlin dot org 2007-06-19 05:00 --- Subject: Bug number PR25061 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-06/msg01294.html -- http://gcc.gnu.org/bugzilla/sh

[Bug fortran/25061] procedure name conflict

2007-05-18 Thread dfranke at gcc dot gnu dot org
--- Comment #2 from dfranke at gcc dot gnu dot org 2007-05-18 15:49 --- I had a short look at this. The problem is in decl.c:693f: if (sym->attr.flavor != 0 && sym->attr.proc != 0 && (sym->attr.subroutine || sym->attr.function) && sym->attr.if_source

[Bug fortran/25061] procedure name conflict

2005-11-26 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2005-11-26 19:31 --- gfortran doesn't catch that issue: ## Intel ## fortcom: Warning: foo.f90, line 2: This name has not been given an explicit type. [I] SUBROUTINE S1(I) ---^ fortcom: Warning: foo.f90, line 4: This na