This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52552] New: Internal compiler error when trying to allocate non-allocatable object giving a dynamic type
- From: "gccbgz.lionm at xoxy dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 10 Mar 2012 14:58:25 +0000
- Subject: [Bug fortran/52552] New: Internal compiler error when trying to allocate non-allocatable object giving a dynamic type
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52552
Bug #: 52552
Summary: Internal compiler error when trying to allocate
non-allocatable object giving a dynamic type
Classification: Unclassified
Product: gcc
Version: 4.4.6
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: gccbgz.lionm@xoxy.net
Created attachment 26872
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26872
erroneous code causing GFortran to crash
GFortran casts an internal error with the simple attached code using some new
OO features of Fortran:
# gfortran oo_err.f90
f951: internal compiler error: Speicherzugriffsfehler
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
The code is obviously erroneous; the bug is that GFortran crashes instead of
giving graful explanations.
Note: GFortran does behave if you omit "te::" in the allocate statement.