From: Paolo Bonzini <bonzini@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
bug-gnulib@gnu.org, 14404@debbugs.gnu.org
Subject: bug#14404: regexp_exec thread-unsafe
Date: Thu, 30 May 2013 09:28:48 +0200 [thread overview]
Message-ID: <51A6FFB0.4000004__24194.9740601287$1369899000$gmane$org@gnu.org> (raw)
In-Reply-To: <51A6A489.2060101@cs.ucla.edu>
Il 30/05/2013 02:59, Paul Eggert ha scritto:
> On 05/26/2013 03:11 PM, Paolo Bonzini wrote:
>> Use the lock module instead.
>
> Adding the lock module should work. But this will require
> some reengineering of Guile, so that Guile uses the lock module
> rather than its own thread packaging. Another possibility, which
> might be a bit simpler, would be for Guile to pretend to
> have the lock module. It could do that by creating a file
> glthread/lock.h that looks something like this:
>
> #include "../libguile/threads.h"
> #define gl_lock_define(class, name) class scm_i_pthread_mutex_t name;
> #define glthread_lock_init scm_i_pthread_mutex_init
> #define glthread_lock_destroy scm_i_pthread_mutex_destroy
> #define glthread_lock_lock scm_i_pthread_mutex_lock
> #define glthread_lock_unlock scm_i_pthread_mutex_lock_unlock
>
> and by putting AC_DEFINE([GNULIB_LOCK]) into configure.ac.
>
Whatever, all I care about is gnulib code not reinventing the wheel and
observing --disable-threads/gl_THREADLIB_DEFAULT_NO.
Paolo
next prev parent reply other threads:[~2013-05-30 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 21:21 regexp_exec thread-unsafe Ludovic Courtès
2013-05-15 7:34 ` bug#14404: " Ludovic Courtès
2013-05-19 21:30 ` Paul Eggert
2013-05-20 14:20 ` bug#14404: " Ludovic Courtès
[not found] ` <87d2slu413.fsf@gnu.org>
2013-05-26 22:11 ` Paolo Bonzini
[not found] ` <51A288AD.4070405@gnu.org>
2013-05-30 0:59 ` Paul Eggert
[not found] ` <51A6A489.2060101@cs.ucla.edu>
2013-05-30 7:28 ` Paolo Bonzini [this message]
2014-03-11 23:15 ` Ludovic Courtès
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='51A6FFB0.4000004__24194.9740601287$1369899000$gmane$org@gnu.org' \
--to=bonzini@gnu.org \
--cc=14404@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).