unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Jose E. Marchesi" <jemarch@gnu.org>, guile-devel@gnu.org
Cc: ludo@gnu.org
Subject: Re: [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized
Date: Tue, 7 Feb 2023 13:29:47 +0100	[thread overview]
Message-ID: <42481ef3-1590-1aaa-aaf3-6405918dcbd5@telenet.be> (raw)
In-Reply-To: <87ttzybq3m.fsf@gnu.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1033 bytes --]


 > [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized
On 06-02-2023 19:34, Jose E. Marchesi wrote:
> 
> Hello Guile hackers.
> 
> We are in the process of integrating GNU poke[1] in GDB by mean of
> libpoke.
> 
> Problem is, libpoke uses the Boehm GC, as guile does.  We are working on
> switching to an ad-hoc exact collector, but it will get some time.
> 
> So, in the interim, we may:
> 
> 1) Make both libguile and libpoke to do GC_INIT conditionally, only if
>     no one else has initialized the collector before.  This is already in
>     poke master.  A suggested (untested!) patch for guile below. > [...]

According to the Boehm GC documentation, this 'conditional 
initialisation' is unnecessary:

/* Portable clients should call this at the program start-up.  More   */
/* over, some platforms require this call to be done strictly from the*/
/* primordial thread.  **Multiple invocations are harmless.**         */
#define GC_INIT() [...]

(emphasis added).

Greetings,
Maxime

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2023-02-07 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 18:34 [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized Jose E. Marchesi
2023-02-06 20:56 ` Jean Abou Samra
2023-02-06 21:05   ` Jose E. Marchesi
2023-02-07 12:29 ` Maxime Devos [this message]
2023-02-20 10:06   ` Ludovic Courtès
2023-02-20 18:01     ` Maxime Devos
2023-02-20 22:00     ` Hans Åberg

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42481ef3-1590-1aaa-aaf3-6405918dcbd5@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-devel@gnu.org \
    --cc=jemarch@gnu.org \
    --cc=ludo@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).