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/68800] Fortran FE produces many memory leaks Date: Mon, 08 May 2023 05:56:22 +0000 [thread overview] Message-ID: <bug-68800-4-GUJFpi1VCi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68800-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68800 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Bernhard Reutner-Fischer <aldot@gcc.gnu.org>: https://gcc.gnu.org/g:2521390dd2f8e554ecccb380e0efd7aa21cd4b5f commit r14-567-g2521390dd2f8e554ecccb380e0efd7aa21cd4b5f Author: Bernhard Reutner-Fischer <aldot@gcc.gnu.org> Date: Sun May 7 00:02:21 2023 +0200 Fortran: Fix mpz and mpfr memory leaks [PR fortran/68800] gcc/fortran/ChangeLog: PR fortran/68800 * expr.cc (find_array_section): Fix mpz memory leak. * simplify.cc (gfc_simplify_reshape): Fix mpz memory leaks in error paths.
prev parent reply other threads:[~2023-05-08 5:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-68800-4@http.gcc.gnu.org/bugzilla/> 2021-11-09 20:57 ` cvs-commit at gcc dot gnu.org 2021-11-09 21:31 ` aldot at gcc dot gnu.org 2023-02-24 20:45 ` anlauf at gcc dot gnu.org 2023-05-08 5:56 ` cvs-commit at gcc dot gnu.org [this message]
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-68800-4-GUJFpi1VCi@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).