search for: pthread_mutexattr_t

...s: static const bool pthread_enabled = *static_cast<bool>(pthread_mutex_init)*; * Shall we update or remove the comment?* Note: If we rollback the code, then 2 warnings will be generated: lib/Support/Mutex.cpp:55: warning: the address of ‘int pthread_mutex_init( pthread_mutex_t*, const pthread_mutexattr_t*)’ will always evaluate as ‘true’ lib/Support/RWMutex.cpp:57: warning: the address of ‘int pthread_mutex_init( pthread_mutex_t*, const pthread_mutexattr_t*)’ will always evaluate as ‘true’ Thanks, Logan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http:/...

Hi Jeremy,   I got some info on that topic from the illumos devs:   > It's a sporadic issue, you're lucky enough to not encounter it on 4.9.5. > > I confirmed in 4.10.2, it happens: > > winbindd.log:  tdb(/tmw-nas-3p/samba/var/lock/gencache.tdb): tdb_open_ex: tdb_mutex_init failed for /tmw-nas-3p/samba/var/lock/gencache.tdb: Device busy > > So either apply OS fix, or

...eturned to indicate the error. ... ERRORS ... The pthread_mutexattr_settype() function will fail if: [EINVAL] Invalid value for attr, or invalid value for type. """ This does not happen (at least not in libthr): """ int _pthread_mutexattr_settype(pthread_mutexattr_t *attr, int type) { int ret; if (attr == NULL || *attr == NULL || type >= PTHREAD_MUTEX_TYPE_MAX) { errno = EINVAL; ret = -1; } else { (*attr)->m_type = type; ret = 0; } return(ret); } &...

...- a/tools/libxl/libxl_internal.c Sat Jan 14 19:04:48 2012 +0100 +++ b/tools/libxl/libxl_internal.c Sat Jan 14 19:04:48 2012 +0100 @@ -296,6 +296,33 @@ int libxl__file_reference_unmap(libxl_fi return 0; } +_hidden int libxl__init_recursive_mutex(libxl_ctx *ctx, pthread_mutex_t *lock) +{ + pthread_mutexattr_t attr; + int rc = 0; + + if (pthread_mutexattr_init(&attr) != 0) { + LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, + "Failed to init mutex attributes\n"); + return ERROR_FAIL; + } + if (pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECU...

> Ok, I am developing an intrinsic instruction and I have the codegen > working (and tested). However, some of the more complex cases of the > intrinsic are reducable to LLVM + simpler cases of the intrinsic. How > would I go about conditionally reducing the intrinsic? I could deal > with the issue in the codegen, but that gets ugly quickly. > > Andrew I suppose you could

Ok, I am developing an intrinsic instruction and I have the codegen working (and tested). However, some of the more complex cases of the intrinsic are reducable to LLVM + simpler cases of the intrinsic. How would I go about conditionally reducing the intrinsic? I could deal with the issue in the codegen, but that gets ugly quickly. Andrew -------------- next part -------------- A non-text

...-------------- next part -------------- target endian = little target pointersize = 32 %struct..TorRec = type { int, void ()* } %struct.TorRec = type { int, void ()* } %struct.timeval = type { int, int } %typedef.__sigset_t = type { [32 x uint] } %typedef.fd_set = type { [32 x int] } %typedef.pthread_mutexattr_t = type { int } %union.nfsctl_res3. = type opaque %.str_1 = internal constant [13 x sbyte] c"Hello World\0A\00" ; <[13 x sbyte]*> [#uses=1] %errno = internal global int 0 ; <int*> [#uses=1] %Initialized.0__ = internal global bool false ; <bool*> [#uses=2] implementat...

...as a separate attachment). diff -u -r src.old/auth-pam.c src/auth-pam.c --- src.old/auth-pam.c Wed Oct 29 12:37:08 2003 +++ src/auth-pam.c Wed Oct 29 12:37:07 2003 @@ -128,6 +128,69 @@ static void sshpam_free_ctx(void *); static struct pam_ctxt *cleanup_ctxt; +#ifdef USE_POSIX_THREADS + +static pthread_mutexattr_t lock_attr; +static pthread_mutex_t sshpam_handle_lock; +static int sshpam_handle_lock_ready = 0; +static int sshpam_handle_lock_count = 0; +static pid_t process_id = 0; + +/* On Solaris, Linux and Darwin, PAM routines are said to only be + * thread-safe if each thread has a different PAM handle (wh...

I have a new problem: Register RBP is used in a function foo. (I am not allocating RBP to any virtual register, the instances of RBP in function foo are in the machine code when my register allocator starts.) Function foo calls function bar. Register RBP is not saved across the call, though it is live after the call. Function bar includes a virtual register. The code that I'm using to

...struct __pthread_mutex_s { int __lock; unsigned int __count; int __owner; unsigned int __nusers; int __kind; int __spins; __pthread_list_t __list; } __data; char __size[40]; long int __align; } pthread_mutex_t; typedef union { char __size[4]; int __align; } pthread_mutexattr_t; typedef union { struct { int __lock; unsigned int __futex; __extension__ unsigned long long int __total_seq; __extension__ unsigned long long int __wakeup_seq; __extension__ unsigned long long int __woken_seq; void *__mutex; unsigned int __nwaiters; unsigned int...