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/107560] ICE in gfc_get_derived_type, at fortran/trans-types.cc:2811 Date: Fri, 24 Mar 2023 20:50:49 +0000 [thread overview] Message-ID: <bug-107560-4-gHZE7Eq7Uq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107560-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107560 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.3.1, 12.2.1, 13.0 CC| |anlauf at gcc dot gnu.org Known to fail| |11.3.0, 12.2.0 --- Comment #1 from anlauf at gcc dot gnu.org --- This used to fail, but appears to have been fixed in the meantime. A possible candidate for variant z2.f90 seems the fix for pr103413. While looking at valgrind output with current trunk, I see a memleak for the BOZ case that is obviously plugged by: diff --git a/gcc/fortran/expr.cc b/gcc/fortran/expr.cc index 4662328bf31..7fb33f81788 100644 --- a/gcc/fortran/expr.cc +++ b/gcc/fortran/expr.cc @@ -466,6 +466,10 @@ free_expr0 (gfc_expr *e) mpc_clear (e->value.complex); break; + case BT_BOZ: + free (e->boz.str); + break; + default: break; } This might have been overseen during the BOZ rework. Regtesting ...
next prev parent reply other threads:[~2023-03-24 20:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-07 18:16 [Bug fortran/107560] New: " gscfq@t-online.de 2023-03-24 20:50 ` anlauf at gcc dot gnu.org [this message] 2023-03-24 20:59 ` [Bug fortran/107560] " kargl at gcc dot gnu.org 2023-03-24 21:07 ` anlauf at gcc dot gnu.org 2023-03-24 21:20 ` anlauf 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-107560-4-gHZE7Eq7Uq@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).