public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58436] New: [4.9 Regression][OOP] ICE (segfault) in generate_finalization_wrapper for CLASS(*)
Date: Mon, 16 Sep 2013 18:42:00 -0000	[thread overview]
Message-ID: <bug-58436-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58436

            Bug ID: 58436
           Summary: [4.9 Regression][OOP] ICE (segfault) in
                    generate_finalization_wrapper for CLASS(*)
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org

The following code leads to an ICE; while finalization is a new 4.9 feature,
the code doesn't require it (and works with GCC 4.8). Hence, I labelled it as
regression.


class(*), allocatable :: var
end


Crashes the compiler with a segfault at

0x572cbf generate_finalization_wrapper
        ../../gcc/fortran/class.c:1518
0x572cbf gfc_find_derived_vtab(gfc_symbol*)
        ../../gcc/fortran/class.c:2317
0x5757cd gfc_build_class_symbol(gfc_typespec*, symbol_attribute*,
gfc_array_spec**, bool)
        ../../gcc/fortran/class.c:652


             reply	other threads:[~2013-09-16 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 18:42 burnus at gcc dot gnu.org [this message]
2013-09-16 18:46 ` [Bug fortran/58436] " dominiq at lps dot ens.fr
2013-09-18  5:43 ` burnus at gcc dot gnu.org
2013-09-25 19:56 ` burnus at gcc dot gnu.org
2013-09-25 20:13 ` burnus at gcc dot gnu.org

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-58436-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).