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/58618] ICE with character substring and ASSOCIATE Date: Sat, 05 Oct 2013 10:32:00 -0000 [thread overview] Message-ID: <bug-58618-4-QhNeYLH9SQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58618-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58618 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2013-10-05 CC| |burnus at gcc dot gnu.org Summary|ICE with character array |ICE with character |and ASSOCIATE |substring and ASSOCIATE Ever confirmed|0 |1 Known to fail| |4.8.1, 4.9.0 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- The ICE occurs in resolve_fl_variable 10795 e = sym->ts.u.cl->length; Here, sym is "x" and ts.u.cl == NULL. Without the substring, ts.u.cl matches "s"'s ts.u.cl (same pointer address). The variable is set in parse.c's parse_associate: 3404 sym->ts = a->target->ts; If the RHS is not a substring, it works. If it is, a->target->ts.u.cl is NULL and the length is only in the REF_SUBSTRING expression at a->target->ref->next->u.ss.length->length
prev parent reply other threads:[~2013-10-05 10:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-04 12:47 [Bug fortran/58618] New: ICE with character array " vladimir.fuka at gmail dot com 2013-10-05 10:32 ` burnus at gcc dot gnu.org [this message]
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-58618-4-QhNeYLH9SQ@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).