public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95585] ICE in gfc_check_reshape, at fortran/check.c:4751 Date: Mon, 08 Jun 2020 21:03:43 +0000 [thread overview] Message-ID: <bug-95585-4-r7imVKGBxq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95585-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95585 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org Ever confirmed|0 |1 Priority|P3 |P4 Last reconfirmed| |2020-06-08 Status|UNCONFIRMED |NEW --- Comment #1 from kargl at gcc dot gnu.org --- Index: gcc/fortran/check.c =================================================================== --- gcc/fortran/check.c (revision 280157) @@ -4720,7 +4728,8 @@ gfc_check_reshape (gfc_expr *source, gfc_expr *shape, && shape->ref->u.ar.as->lower[0]->ts.type == BT_INTEGER && shape->ref->u.ar.as->upper[0]->expr_type == EXPR_CONSTANT && shape->ref->u.ar.as->upper[0]->ts.type == BT_INTEGER - && shape->symtree->n.sym->attr.flavor == FL_PARAMETER) + && shape->symtree->n.sym->attr.flavor == FL_PARAMETER + && shape->symtree->n.sym->value) { int i, extent; gfc_expr *e, *v;
next prev parent reply other threads:[~2020-06-08 21:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 18:47 [Bug fortran/95585] New: " gscfq@t-online.de 2020-06-08 21:03 ` kargl at gcc dot gnu.org [this message] 2020-06-22 12:15 ` [Bug fortran/95585] " cvs-commit at gcc dot gnu.org 2020-06-23 6:31 ` markeggleston at gcc dot gnu.org 2020-07-26 9:05 ` cvs-commit at gcc dot gnu.org 2020-07-26 10:56 ` cvs-commit 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-95585-4-r7imVKGBxq@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).