Date: Tue, 23 Jan 2018 09:55:50 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 220767] lang/beignet: hangs if consumer is not linked against libpthread after jemalloc 5.0.0 update Message-ID: <bug-220767-13406-61wRvMEqA4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220767-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-220767-13406@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220767 --- Comment #5 from Alexey Dokuchaev <danfe@FreeBSD.org> --- (In reply to Jan Beich from comment #4) FWIW, I've tried to play with malloc_mutex_first_thread() implementation, JEMALLOC_MUTEX_INIT_CB (+ some related macros), using different atomics implementation in jemalloc 5.0.0, all without any luck. For the record, I'm including this advice from John Baldwin: > I wonder if it is tripping over pthread_once not working in libc. The st= ub > for pthread_once in libc is a nop and has been for a long time. I added > a functioning stub (called _libc_once) to libc for it's internal use (the= re > is a _once() wrapper that will call _pthread_once when using libpthread a= nd > _libc_once otherwise). It might be interesting to build jemalloc with > '-Dpthread_once=3D_once' to see if that makes a difference? I've tried this as well and it did not help. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220767-13406-61wRvMEqA4>