public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gccbgz.lionm at xoxy dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52552] New: Internal compiler error when trying to allocate non-allocatable object giving a dynamic type
Date: Sat, 10 Mar 2012 14:58:00 -0000	[thread overview]
Message-ID: <bug-52552-4@http.gcc.gnu.org/bugzilla/> (raw)

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.


             reply	other threads:[~2012-03-10 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 14:58 gccbgz.lionm at xoxy dot net [this message]
2012-03-10 19:10 ` [Bug fortran/52552] [OOP] ICE " burnus at gcc dot gnu.org
2012-03-12 11:24 ` burnus at gcc dot gnu.org
2012-03-12 11:30 ` burnus at gcc dot gnu.org
2012-06-07 16:26 ` janus at gcc dot gnu.org
2012-06-08  7:56 ` janus at gcc dot gnu.org
2012-06-08 17:26 ` janus at gcc dot gnu.org
2012-06-08 17:39 ` janus at gcc dot gnu.org
2012-06-08 18:56 ` gccbgz.lionm at xoxy dot net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52552-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).