public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97896] [11 Regression] ICE in gfc_trans_assignment_1, at fortran/trans-expr.c:11156 Date: Wed, 18 Nov 2020 21:48:22 +0000 [thread overview] Message-ID: <bug-97896-4-xS1uIMJDbz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97896-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97896 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW CC| |anlauf at gcc dot gnu.org --- Comment #2 from anlauf at gcc dot gnu.org --- Reverting the following snippet from my fix attempt for pr91651: diff --git a/gcc/fortran/iresolve.c b/gcc/fortran/iresolve.c index c2a4865f28f..994a9af4eb8 100644 --- a/gcc/fortran/iresolve.c +++ b/gcc/fortran/iresolve.c @@ -1296,11 +1296,7 @@ gfc_resolve_index_func (gfc_expr *f, gfc_actual_arglist *a) f->ts.type = BT_INTEGER; if (kind) - { - f->ts.kind = mpz_get_si ((kind)->value.integer); - a_back->next = NULL; - gfc_free_actual_arglist (a_kind); - } + f->ts.kind = mpz_get_si ((kind)->value.integer); else f->ts.kind = gfc_default_integer_kind; fixes the current PR, but breaks testcase index_4.f90
next prev parent reply other threads:[~2020-11-18 21:48 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-18 16:37 [Bug fortran/97896] New: " gscfq@t-online.de 2020-11-18 17:57 ` [Bug fortran/97896] " dominiq at lps dot ens.fr 2020-11-18 21:48 ` anlauf at gcc dot gnu.org [this message] 2020-11-19 7:34 ` rguenth at gcc dot gnu.org 2020-11-19 20:28 ` anlauf at gcc dot gnu.org 2020-11-20 14:55 ` mikael at gcc dot gnu.org 2020-11-20 20:48 ` anlauf at gcc dot gnu.org 2020-11-21 18:00 ` mikael at gcc dot gnu.org 2020-11-21 18:02 ` mikael at gcc dot gnu.org 2020-11-21 18:06 ` mikael at gcc dot gnu.org 2021-04-27 11:39 ` [Bug fortran/97896] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-08-07 18:38 ` mikael at gcc dot gnu.org 2021-11-12 12:11 ` cvs-commit at gcc dot gnu.org 2021-11-16 20:36 ` cvs-commit at gcc dot gnu.org 2021-11-17 10:45 ` mikael at gcc dot gnu.org 2022-01-16 18:16 ` cvs-commit at gcc dot gnu.org 2022-01-16 21:20 ` cvs-commit at gcc dot gnu.org 2022-01-16 21:20 ` 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-97896-4-xS1uIMJDbz@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).