From: Andrea Corallo <andrea.corallo@arm.com>
To: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
Cc: "Marc Nieper-Wißkirchen via Jit" <jit@gcc.gnu.org>,
"Alex Coplan" <Alex.Coplan@arm.com>,
"Mark Wielaard" <mark@klomp.org>,
nd@arm.com
Subject: Re: Memory leaks (detected by Valgrind)
Date: Fri, 17 Dec 2021 19:48:02 +0100 [thread overview]
Message-ID: <gkrfsqrvzj1.fsf@arm.com> (raw)
In-Reply-To: <CAEYrNrTPxHQ=ri0t2m1PPQx-Dzk-wZD70s8sVoKz+2BZb5kkxw@mail.gmail.com> ("Marc =?utf-8?Q?Nieper-Wi=C3=9Fkirchen=22's?= message of "Fri, 17 Dec 2021 18:53:45 +0100")
Marc Nieper-Wißkirchen <marc.nieper+gnu@gmail.com> writes:
> Speaking of parallelism: When I tried to find where the memory losses come from, I saw a lot of global variables like `link_command_spec' in `gcc.c'. Does it mean that compiling the context is not thread-safe? (I may have missed that in libgccjit's documentation.)
It is thread safe because in practice the compilation itself it's all
guarded by a mutex, see [1] for more details.
That's another good reason (I forgot to mention) why sub-processes are a
good option for Emacs (we run many compilations in parallel).
Best Regards
Andrea
PS please use ascii only email on list.
[1] <https://gcc.gnu.org/onlinedocs/jit/internals/index.html#design-notes>
next prev parent reply other threads:[~2021-12-17 18:48 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
2021-12-17 16:07 ` Andrea Corallo
2021-12-17 17:53 ` Marc Nieper-Wißkirchen
2021-12-17 18:48 ` Andrea Corallo [this message]
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=gkrfsqrvzj1.fsf@arm.com \
--to=andrea.corallo@arm.com \
--cc=Alex.Coplan@arm.com \
--cc=jit@gcc.gnu.org \
--cc=marc.nieper+gnu@gmail.com \
--cc=mark@klomp.org \
--cc=nd@arm.com \
/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).