From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Subject: [PATCH 0/3] Fix mpfr and mpz memory leaks
Date: Sun, 2 Apr 2023 17:05:12 +0200 [thread overview]
Message-ID: <20230402150515.40826-1-rep.dot.nop@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2303061129030.18795@jbgna.fhfr.qr>
From: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Hi!
These patches for the go, rust and fortran frontends fix the mpfr and
mpz memory leaks my coccinelle script found.
Bootstrapped and regtested without regressions on x86_64-unknown-linux,
including go,rust,fortran.
Ok for trunk for the fortran bits?
I'd hope that go and rust can apply the respective patches upstream.
Bernhard Reutner-Fischer (3):
go: Fix memory leak in Integer_expression
rust: Fix memory leak in compile_{integer,float}_literal
Fortran: Fix mpz and mpfr memory leaks
gcc/fortran/array.cc | 3 +++
gcc/fortran/expr.cc | 8 ++++----
gcc/fortran/simplify.cc | 7 ++++++-
gcc/go/gofrontend/expressions.cc | 5 +++++
gcc/rust/backend/rust-compile-expr.cc | 7 +++++++
5 files changed, 25 insertions(+), 5 deletions(-)
--
2.30.2
next prev parent reply other threads:[~2023-04-02 15:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 10:11 [PATCH] [RFC] RAII auto_mpfr and autp_mpz Richard Biener
2023-03-06 10:44 ` Jonathan Wakely
2023-03-06 11:01 ` Richard Biener
2023-03-06 11:03 ` Jonathan Wakely
2023-03-06 11:10 ` Jakub Jelinek
2023-03-06 11:29 ` Richard Biener
2023-03-07 18:51 ` Bernhard Reutner-Fischer
2023-03-07 19:03 ` Jakub Jelinek
2023-04-02 15:05 ` Bernhard Reutner-Fischer [this message]
2023-04-02 15:05 ` [PATCH 1/3] go: Fix memory leak in Integer_expression Bernhard Reutner-Fischer
2023-04-02 15:05 ` [PATCH 2/3] rust: Fix memory leak in compile_{integer,float}_literal Bernhard Reutner-Fischer
2023-04-02 15:05 ` [PATCH 3/3] Fortran: Fix mpz and mpfr memory leaks Bernhard Reutner-Fischer
2023-04-03 19:50 ` Harald Anlauf
2023-04-03 19:50 ` Harald Anlauf
2023-04-03 21:42 ` Bernhard Reutner-Fischer
2023-04-17 19:47 ` ping " Bernhard Reutner-Fischer
2023-04-17 22:18 ` Steve Kargl
2023-05-08 6:00 ` Bernhard Reutner-Fischer
2023-03-07 19:15 ` [PATCH] [RFC] RAII auto_mpfr and autp_mpz Alexander Monakov
2023-03-07 21:35 ` Jonathan Wakely
2023-03-07 21:51 ` Alexander Monakov
2023-03-07 21:54 ` Jonathan Wakely
2023-03-07 21:59 ` Marek Polacek
2023-03-08 7:25 ` Richard Biener
2023-03-08 10:13 ` Jonathan Wakely
2023-03-08 10:33 ` Jakub Jelinek
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=20230402150515.40826-1-rep.dot.nop@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=aldot@gcc.gnu.org \
--cc=gcc-patches@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: link
Be 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).