This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52325] New: unclear error: Unclassifiable statement
- From: "kloedej at knmi dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 21 Feb 2012 10:17:37 +0000
- Subject: [Bug fortran/52325] New: unclear error: Unclassifiable statement
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52325
Bug #: 52325
Summary: unclear error: Unclassifiable statement
Classification: Unclassified
Product: gcc
Version: 4.6.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: kloedej@knmi.nl
The given example code generates this error:
unclassifiable.F90:9.4:
cc%a = 1
1
Error: Unclassifiable statement at (1)
while in fact it would be much more helpfull if the error would clearly state
that the symbol is not yet defined (as the commented out lines do):
unclassifiable.F90:16.5:
d=1
1
Error: Symbol 'd' at (1) has no IMPLICIT type
Especially in larger modules/programs having a clear error in case of this kind
of variable naming msitakes/typos could save a lot of debugging time for
gfortran users.
Example code:
module test_unclassifiable
implicit none
type test
integer :: a
end type test
contains
subroutine test_sub1(c)
type(test), intent(out) :: c
cc%a = 1
end subroutine test_sub1
! subroutine test_sub2(c)
! integer :: c
! d=1
! end subroutine test_sub2
end module test_unclassifiable