[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#14404: regexp_exec thread-unsafe
From: |
Paolo Bonzini |
Subject: |
bug#14404: regexp_exec thread-unsafe |
Date: |
Thu, 30 May 2013 09:28:48 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 |
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