Bug 15493 - [fortran] ICE on wrong code
Summary: [fortran] ICE on wrong code
Status: RESOLVED DUPLICATE of bug 13575
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 4.0.0
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: ice-on-invalid-code
Depends on: 13575 15481
Blocks:
  Show dependency tree / graph
 
Reported: 2004-05-17 13:23 UTC by Martin Reinecke
Modified: 2004-10-30 21:12 UTC (History)
2 users (show)

See Also:
Host: i686-pc-linux-gnu
Target: i686-pc-linux-gnu
Build: i686-pc-linux-gnu
Known to work:
Known to fail: 4.0.0
Last reconfirmed: 2004-05-17 13:39:00

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Reinecke 2004-05-17 13:23:46 UTC 
The following (ill-formed, I think) code causes current gfortran to crash
with an ICE:

module foo
implicit none

public bar

contains

end module foo

~/tmp>gfortran -v -c bug.f90
Reading specs from /afs/mpa/data/martin/ugcc/lib/gcc/i686-pc-linux-gnu/3.5.0/specs
Configured with: /scratch/gcc/configure --quiet
--prefix=/afs/mpa/data/martin/ugcc --enable-languages=c++,f95
--with-gmp=/afs/mpa/data/martin/mygmp --disable-checking
Thread model: posix
gcc version 3.5.0 20040517 (experimental)
 /afs/mpa/data/martin/ugcc/libexec/gcc/i686-pc-linux-gnu/3.5.0/f951 bug.f90
-quiet -dumpbase bug.f90 -mtune=pentiumpro -auxbase bug -version -o /tmp/ccsbxSgf.s
GNU F95 version 3.5.0 20040517 (experimental) (i686-pc-linux-gnu)
        compiled by GNU C version 3.5.0 20040517 (experimental).
GGC heuristics: --param ggc-min-expand=63 --param ggc-min-heapsize=63317
bug.f90:0: internal compiler error: in gfc_typenode_for_spec, at
fortran/trans-types.c:303
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
Comment 1 Andrew Pinski 2004-05-17 13:39:00 UTC 
Confirmed, I think this is a dup of bug 13575
Comment 2 Tobias Schlüter 2004-05-17 14:22:41 UTC 
Indeed, this is the same problem as PR 13575.

*** This bug has been marked as a duplicate of 13575 ***