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/98023] ICE: free_expr0(): Bad expr type Date: Mon, 30 Nov 2020 21:49:40 +0000 [thread overview] Message-ID: <bug-98023-4-ktGXULw54X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98023-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98023 --- Comment #3 from anlauf at gcc dot gnu.org --- The patch in comment#1 does not work for me on x86_64-pc-linux-gnu. In decl.c: 6242 cleanup: 6243 if (saved_kind_expr) 6244 gfc_free_expr (saved_kind_expr); 6245 if (type_param_spec_list) 6246 gfc_free_actual_arglist (type_param_spec_list); (gdb) p type_param_spec_list->expr->expr_type $177 = 42350080 So type_param_spec_list really gets screwed up.
next prev parent reply other threads:[~2020-11-30 21:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-27 3:38 [Bug fortran/98023] New: " asolokha at gmx dot com 2020-11-27 4:29 ` [Bug fortran/98023] " kargl at gcc dot gnu.org 2020-11-27 11:22 ` marxin at gcc dot gnu.org 2020-11-30 21:49 ` anlauf at gcc dot gnu.org [this message] 2023-06-30 8:18 ` [Bug fortran/98023] ICE: [PDT] " pault 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-98023-4-ktGXULw54X@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).