From: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
To: Andrea Corallo <andrea.corallo@arm.com>
Cc: "Marc Nieper-Wißkirchen via Jit" <jit@gcc.gnu.org>,
"Alex Coplan" <Alex.Coplan@arm.com>,
"Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>,
"Mark Wielaard" <mark@klomp.org>
Subject: Re: Memory leaks (detected by Valgrind)
Date: Fri, 17 Dec 2021 16:11:06 +0100 [thread overview]
Message-ID: <CAEYrNrSDdEweauiP3MKysPKLGF4hj9ev20OF3TCx8FYFVQT20Q@mail.gmail.com> (raw)
In-Reply-To: <gkrzgozwaco.fsf@arm.com>
Am Fr., 17. Dez. 2021 um 15:54 Uhr schrieb Andrea Corallo <
andrea.corallo@arm.com>:
> Marc Nieper-Wißkirchen via Jit <jit@gcc.gnu.org> writes:
>
> > Am Fr., 17. Dez. 2021 um 11:52 Uhr schrieb Alex Coplan <
> Alex.Coplan@arm.com
> >>:
> >
> >> Hi,
> >>
> >> > -----Original Message-----
> >> > From: Jit <jit-bounces+alex.coplan=arm.com@gcc.gnu.org> On Behalf Of
> >> Marc
> >> > Nieper-Wißkirchen via Jit
> >> > Sent: 17 December 2021 10:29
> >> > To: Mark Wielaard <mark@klomp.org>
> >> > Cc: Marc Nieper-Wißkirchen <marc.nieper+gnu@gmail.com>;
> jit@gcc.gnu.org
> >> > Subject: Re: Memory leaks (detected by Valgrind)
> >> >
> >> > Thanks!
> >> >
> >> > With `--enable-valgrind-annotations`, the "uses of uninitialized
> values"
> >> > have gone away, but a lot of small leaks are still present:
> >>
> >> Memory leaks with libgccjit are a known issue, see
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63854
> >
> >
> > Oh, that the bug has been open so long and is still open is unfortunate
> as
> > a process using libgccjit usually lasts a lot longer than a single
> compiler
> > run by gcc.
>
> That's correct, in Emacs we have to work around this running a
> sub-processes for compilation tasks.
>
This weakens the usefulness of libgccjit considerably, doesn't it? If I
have to start a new process to invoke it, only a bit is won compared to
writing out C and using the C frontend of GCC through exec, no? How to you
pass back the result of the compilation from the subprocess to the original
process in Emacs?
PS How difficult is it to fix the memory leaks?
next prev parent reply other threads:[~2021-12-17 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 17:17 Marc Nieper-Wißkirchen
2021-12-16 22:00 ` Marc Nieper-Wißkirchen
2021-12-16 22:26 ` Mark Wielaard
2021-12-17 10:29 ` Marc Nieper-Wißkirchen
2021-12-17 10:52 ` Alex Coplan
2021-12-17 14:03 ` Marc Nieper-Wißkirchen
2021-12-17 14:54 ` Andrea Corallo
2021-12-17 15:11 ` Marc Nieper-Wißkirchen [this message]
2021-12-17 16:07 ` Andrea Corallo
2021-12-17 17:53 ` Marc Nieper-Wißkirchen
2021-12-17 18:48 ` Andrea Corallo
2021-12-17 23:22 ` David Malcolm
2021-12-18 13:57 ` Marc Nieper-Wißkirchen
2021-12-18 16:45 ` David Malcolm
2021-12-18 17:50 ` Marc Nieper-Wißkirchen
2021-12-18 19:36 ` Marc Nieper-Wißkirchen
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=CAEYrNrSDdEweauiP3MKysPKLGF4hj9ev20OF3TCx8FYFVQT20Q@mail.gmail.com \
--to=marc.nieper+gnu@gmail.com \
--cc=Alex.Coplan@arm.com \
--cc=andrea.corallo@arm.com \
--cc=jit@gcc.gnu.org \
--cc=mark@klomp.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).