From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 22608@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#22608: Module system thread unsafety and .go compilation
Date: Mon, 10 Oct 2022 10:07:56 +0200 [thread overview]
Message-ID: <87v8os3xur.fsf@gnu.org> (raw)
In-Reply-To: <87lepr412m.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 07 Oct 2022 20:21:37 -0400")
Hi!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> For the record, these issues should be fixed in Guile 2.2.4:
>>
>> 533e3ff17 * Serialize accesses to submodule hash tables.
>> 46bcbfa56 * Module import obarrays are accessed in a critical section.
>> 761cf0fb8 * Make module autoloading thread-safe.
>>
>> ‘guix pull’ now defaults to 2.2.4, so we’ll see if indeed those crashes
>> disappear.
>
> I think we haven't seen these in the last 4 years! We still have
> references to https://bugs.gnu.org/15602 in our code base though;
> although the upstream issue appears to have been fixed. Could we remove
> the workarounds now?
The module thread-safety issue discussed here appears to be done.
However the workarounds for <https://bugs.gnu.org/15602> must remain:
that specific issue is still there.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-10-10 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 20:02 Module system thread unsafety and .go compilation Taylan Ulrich Bayırlı/Kammer
2016-02-10 13:50 ` bug#22608: " Ludovic Courtès
2016-02-10 13:50 ` Ludovic Courtès
2018-07-03 22:10 ` Ludovic Courtès
[not found] ` <87d0w4ezst.fsf@gnu.org>
2022-10-08 0:21 ` Maxim Cournoyer
2022-10-10 8:07 ` Ludovic Courtès [this message]
2022-10-12 14:24 ` Maxim Cournoyer
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=87v8os3xur.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22608@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.