This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/48776] New: ICE(segfault) after -std=f95 diagnostic error involving PROCEDURE
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 26 Apr 2011 18:45:54 +0000
- Subject: [Bug fortran/48776] New: ICE(segfault) after -std=f95 diagnostic error involving PROCEDURE
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48776
Summary: ICE(segfault) after -std=f95 diagnostic error
involving PROCEDURE
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: error-recovery, ice-on-invalid-code
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: burnus@gcc.gnu.org
Follow up to bug 48279 comment 7 and 48279 comment 11.
The following program segfaults with -std=f95 after printing the diagnostic:
procedure get1
1
Error: Fortran 2003: PROCEDURE statement at (1)
f951: internal compiler error: Segmentation fault
Valgrind shows tons of errors, starting with:
==22545== Invalid read of size 8
==22545== at 0x52FD8C: resolve_symbol (resolve.c:10004)
==22545== by 0x54BA76: traverse_ns (symbol.c:3379)
==22545== by 0x53919B: resolve_types (resolve.c:13261)
==22545== by 0x52E3D3: gfc_resolve (resolve.c:13357)
The testcase:
interface get
procedure get1
end interface
integer :: h
call set1 (get (h))
contains
subroutine set1 (a)
integer, intent(in) :: a
end subroutine
integer function get1 (s)
integer :: s
end function
end