public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64757] [5 Regression] ICE in fold_convert_loc, at fold-const.c:2353
Date: Sat, 24 Jan 2015 12:24:00 -0000	[thread overview]
Message-ID: <bug-64757-4-snLEYVbOK6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64757-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64757

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|internal compiler error: in |[5 Regression] ICE in
                   |fold_convert_loc, at        |fold_convert_loc, at
                   |fold-const.c:2353           |fold-const.c:2353

--- Comment #3 from janus at gcc dot gnu.org ---
Here is a reduction of the original test case which gives the ICE with trunk,
but compiles cleanly with 4.9:


  type :: Test
  end type

  type :: TestReference
     class(Test), allocatable :: test
  end type

  type(TestReference) :: testList

  testList = TestReference(Test())  ! ICE in fold_convert_loc

end



The backtrace is:

internal compiler error: in fold_convert_loc, bei fold-const.c:2357
0x814255 fold_convert_loc(unsigned int, tree_node*, tree_node*)
    /home/jweil/gcc/gcc50/trunk/gcc/fold-const.c:2357
0x6b16ea alloc_scalar_allocatable_for_subcomponent_assignment
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-expr.c:6403
0x6b16ea gfc_trans_subcomponent_assign
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-expr.c:6497
0x6b087b gfc_trans_structure_assign
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-expr.c:6649
0x6b2104 gfc_conv_structure(gfc_se*, gfc_expr*, int)
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-expr.c:6678
0x6ad46c gfc_conv_expr(gfc_se*, gfc_expr*)
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-expr.c:6848
0x6b32ff gfc_trans_assignment_1
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-expr.c:8553
0x682035 trans_code
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans.c:1650
0x6a2e53 gfc_generate_function_code(gfc_namespace*)
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/trans-decl.c:5844
0x63e470 translate_all_program_units
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/parse.c:5341
0x63e470 gfc_parse_file()
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/parse.c:5538
0x67de95 gfc_be_parse_file
    /home/jweil/gcc/gcc50/trunk/gcc/fortran/f95-lang.c:228


  parent reply	other threads:[~2015-01-24 12:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 22:34 [Bug fortran/64757] New: internal compiler error: " mike at rilee dot net
2015-01-24 11:52 ` [Bug fortran/64757] " dominiq at lps dot ens.fr
2015-01-24 12:20 ` janus at gcc dot gnu.org
2015-01-24 12:24 ` janus at gcc dot gnu.org [this message]
2015-01-24 12:31 ` [Bug fortran/64757] [5 Regression] ICE " dominiq at lps dot ens.fr
2015-01-24 12:35 ` janus at gcc dot gnu.org
2015-01-24 22:25 ` janus at gcc dot gnu.org
2015-01-26 11:33 ` rguenth at gcc dot gnu.org
2015-01-28 13:37 ` pault at gcc dot gnu.org
2015-01-28 14:42 ` pault at gcc dot gnu.org
2015-01-28 16:19 ` dominiq at lps dot ens.fr
2015-02-05  8:06 ` pault at gcc dot gnu.org
2015-02-05  8:09 ` pault at gcc dot gnu.org
2015-02-05  8:45 ` 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-64757-4-snLEYVbOK6@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).