public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antony at cosmologist dot info" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60234] New: OOP internal compiler error: in generate_finalization_wrapper
Date: Sun, 16 Feb 2014 22:55:00 -0000	[thread overview]
Message-ID: <bug-60234-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60234
           Summary: OOP internal compiler error: in
                    generate_finalization_wrapper
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: antony at cosmologist dot info

Created attachment 32146
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32146&action=edit
OOP module implementing lists of arrays of objects (with final)

Problem module attached:

gfortran -cpp -c ObjectLists.f90
f951: internal compiler error: in generate_finalization_wrapper, at
fortran/class.c:1883
0x816b6d9 generate_finalization_wrapper
    ../../gcc-trunk/gcc/fortran/class.c:1883
0x816b6d9 gfc_find_derived_vtab(gfc_symbol*)
    ../../gcc-trunk/gcc/fortran/class.c:2315
0x8169eb7 gfc_find_derived_vtab(gfc_symbol*)
    ../../gcc-trunk/gcc/fortran/class.c:2188
0x816c347 gfc_build_class_symbol(gfc_typespec*, symbol_attribute*,
gfc_array_spec**, bool)
    ../../gcc-trunk/gcc/fortran/class.c:646
0x8172438 build_sym
    ../../gcc-trunk/gcc/fortran/decl.c:1202
0x8177d1e variable_decl
    ../../gcc-trunk/gcc/fortran/decl.c:1980
0x8177d1e gfc_match_data_decl()
    ../../gcc-trunk/gcc/fortran/decl.c:4309
0x81bd5e7 match_word
    ../../gcc-trunk/gcc/fortran/parse.c:65
0x81be6ba match_word
    ../../gcc-trunk/gcc/fortran/parse.c:331
0x81be6ba decode_statement
    ../../gcc-trunk/gcc/fortran/parse.c:331
0x81bfac7 next_free
    ../../gcc-trunk/gcc/fortran/parse.c:784
0x81bfac7 next_statement
    ../../gcc-trunk/gcc/fortran/parse.c:977
0x81c0247 parse_spec
    ../../gcc-trunk/gcc/fortran/parse.c:2784
0x81c21f8 parse_progunit
    ../../gcc-trunk/gcc/fortran/parse.c:4148
0x81c2556 parse_contained
    ../../gcc-trunk/gcc/fortran/parse.c:4087
0x81c36ec parse_module
    ../../gcc-trunk/gcc/fortran/parse.c:4350
0x81c36ec gfc_parse_file()
    ../../gcc-trunk/gcc/fortran/parse.c:4652
0x81ff6c5 gfc_be_parse_file
    ../../gcc-trunk/gcc/fortran/f95-lang.c:188


             reply	other threads:[~2014-02-16 22:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 22:55 antony at cosmologist dot info [this message]
2014-02-17 10:28 ` [Bug fortran/60234] [4.9 Regression] [OOP] ICE in generate_finalization_wrapper at fortran/class.c:1883 janus at gcc dot gnu.org
2014-02-17 10:39 ` janus at gcc dot gnu.org
2014-02-17 11:11 ` janus at gcc dot gnu.org
2014-02-17 11:28 ` janus at gcc dot gnu.org
2014-02-17 12:24 ` janus at gcc dot gnu.org
2014-02-17 13:46 ` janus at gcc dot gnu.org
2014-02-17 14:19 ` janus at gcc dot gnu.org
2014-02-21  9:07 ` janus at gcc dot gnu.org
2014-02-21  9:09 ` janus 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-60234-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).