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/49430] ICE with allocatable length character in interface block Date: Wed, 15 Jun 2011 23:44:00 -0000 [thread overview] Message-ID: <bug-49430-4-3TsKCREOox@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49430-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49430 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code CC| |burnus at gcc dot gnu.org Blocks| |45170 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-06-15 23:43:42 UTC --- I get: test.f90:19:0: internal compiler error: tree check: expected tree that contains 'typed' structure, have '�' in fold_convert_loc, at fold-const.c:1859 ==14082== Invalid read of size 1 ==14082== at 0x72F9B2: fold_convert_loc (fold-const.c:1859) ==14082== by 0xA7D3F6: build_range_type_1 (tree.c:7170) ==14082== by 0x5C8C69: gfc_get_character_type_len_for_eltype (trans-types.c:977) ==14082== by 0x59EA63: gfc_conv_procedure_call (trans-expr.c:3538) ==14082== by 0x59F271: gfc_conv_function_expr (trans-expr.c:4082) ==14082== by 0x597D01: gfc_trans_assignment_1 (trans-expr.c:6112) In trans-expr.c:3538: (gdb) p *ts.u.cl $2 = {length = 0x0, next = 0x0, length_from_typespec = 215 '\327', backend_decl = 0x1535340, passed_length = 0x2aaaacdd7f00, resolved = 6764539} I wonder whether the 3538 type = gfc_get_character_type (ts.kind, ts.u.cl); should be rather: type = gfc_get_character_type (ts.kind, ts->deferred ? NULL_TREE : ts.u.cl);
next prev parent reply other threads:[~2011-06-15 23:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-15 23:14 [Bug fortran/49430] New: " shadowblade at altern dot org 2011-06-15 23:44 ` burnus at gcc dot gnu.org [this message] 2011-06-21 19:41 ` [Bug fortran/49430] " janus at gcc dot gnu.org 2011-06-21 20:22 ` janus at gcc dot gnu.org 2011-06-21 21:19 ` janus at gcc dot gnu.org 2011-06-21 21:37 ` janus at gcc dot gnu.org 2011-06-27 17:05 ` [Bug fortran/49430] [F03] " janus at gcc dot gnu.org 2012-05-13 11:21 ` burnus at gcc dot gnu.org 2012-05-13 11:38 ` burnus at gcc dot gnu.org 2012-09-25 16:15 ` dtemirbulatov at gmail dot com 2012-09-25 16:17 ` dtemirbulatov at gmail dot com
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-49430-4-3TsKCREOox@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: linkBe 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).