This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/25061] procedure name conflict
- From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Nov 2005 19:31:49 -0000
- Subject: [Bug fortran/25061] procedure name conflict
- References: <bug-25061-6642@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla 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 name has not been given an explicit
type. [R]
SUBROUTINE S2(R)
---------------^
fortcom: Warning: foo.f90, line 8: This name has not been given an explicit
type. [I]
SUBROUTINE I1(I)
---------------^
fortcom: Error: foo.f90, line 8: The name of the internal procedure conflicts
with a name in the encompassing scoping unit. [I1]
SUBROUTINE I1(I)
------------^
fortcom: Info: foo.f90, line 8: This variable has not been used. [I]
SUBROUTINE I1(I)
---------------^
compilation aborted for foo.f90 (code 1)
## Portland ##
## Sun ##
SUBROUTINE I1(I)
^
"foo.f90", Line = 8, Column = 13: ERROR: "I1" is a generic-name, therefore it
must not be declared as a internal subroutine.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |accepts-invalid
Last reconfirmed|0000-00-00 00:00:00 |2005-11-26 19:31:49
date| |
Summary|better diagnostic needed |procedure name conflict
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25061