public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108923] memory leak of get_intrinsic_dummy_arg result Date: Sun, 12 Mar 2023 10:48:31 +0000 [thread overview] Message-ID: <bug-108923-4-tgwu5D8hMo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108923-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108923 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Mikael Morin <mikael@gcc.gnu.org>: https://gcc.gnu.org/g:cd65c727fd6d5a252964dbeb3a735daa0a521a89 commit r12-9243-gcd65c727fd6d5a252964dbeb3a735daa0a521a89 Author: Mikael Morin <mikael@gcc.gnu.org> Date: Fri Feb 24 22:11:17 2023 +0100 fortran: Plug leak of associated_dummy memory. [PR108923] This fixes a memory leak by accompanying the release of gfc_actual_arglist elements' memory with a release of the associated_dummy field memory (if allocated). Actual argument copy is adjusted as well so that each copy can free its field independently. PR fortran/108923 gcc/fortran/ChangeLog: * expr.cc (gfc_free_actual_arglist): Free associated_dummy memory. (gfc_copy_actual_arglist): Make a copy of the associated_dummy field if it is set in the original element. (cherry picked from commit 24c9edfa73632276d7698c103f35833f29804d98)
next prev parent reply other threads:[~2023-03-12 10:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-24 12:28 [Bug fortran/108923] New: " rguenth at gcc dot gnu.org 2023-02-24 16:38 ` [Bug fortran/108923] " mikael at gcc dot gnu.org 2023-02-24 19:41 ` mikael at gcc dot gnu.org 2023-02-24 19:42 ` mikael at gcc dot gnu.org 2023-02-24 21:14 ` cvs-commit at gcc dot gnu.org 2023-02-24 21:44 ` anlauf at gcc dot gnu.org 2023-02-25 20:38 ` cvs-commit at gcc dot gnu.org 2023-03-03 14:03 ` rguenth at gcc dot gnu.org 2023-03-12 10:48 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-12 10:48 ` 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-108923-4-tgwu5D8hMo@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).