unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@gnu.org>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: guile-devel@gnu.org,  ludo@gnu.org
Subject: Re: [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized
Date: Mon, 06 Feb 2023 22:05:47 +0100	[thread overview]
Message-ID: <87lelabj2s.fsf@gnu.org> (raw)
In-Reply-To: <29bad7bd-fad4-c835-cad9-488462efbe4f@abou-samra.fr> (Jean Abou Samra's message of "Mon, 6 Feb 2023 21:56:13 +0100")


> 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.
>> 
>> 2) Test to see if the collector works properly.
>> 
>> 3) Do bug-fix releases of both libguile and libpoke so the GDB people
>>    can check for the right version in configure.ac in order to allow
>>    configuring GDB with both libpoke and libguile support.
>> 
>> Does this sound like a plan?
>> Thanks in advance!
>> 
>> [1] https://jemarch.net/poke
>> 
>> diff --git a/libguile/gc.c b/libguile/gc.c
>> index 7717e9bef..36653d373 100644
>> --- a/libguile/gc.c
>> +++ b/libguile/gc.c
>> @@ -462,7 +462,8 @@ scm_storage_prehistory ()
>>    setenv ("GC_MARKERS", "1", 1);
>>  #endif
>>  
>> -  GC_INIT ();
>> +  if(!GC_is_init_called ())
>> +    GC_INIT ();
>>  
>>    size_t heap_size = GC_get_heap_size ();
>>    if (heap_size < DEFAULT_INITIAL_HEAP_SIZE)
>> 
>
>
>
> Isn't that going to cause problems if the configurations clash?
> For example, the scm_storage_prehistory () function that you
> are modifying does
>
> GC_set_all_interior_pointers (0);
>
> If the application that previously initialized the GC relies
> on interior pointer tracing, Guile disabling it is going to
> cause trouble.

Indeed, we would need to agree on these details and come with a
configuration that works with both configurations.



  reply	other threads:[~2023-02-06 21:05 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 [this message]
2023-02-07 12:29 ` Maxime Devos
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=87lelabj2s.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=jean@abou-samra.fr \
    --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).