Displaying 6 results from an estimated 6 matches for "pthread_en".
Did you mean:
pthread_t
2011 Feb 13
0
[LLVMdev] Code/comment seems not synchronized in Mutex.cpp and RWMutex.cpp
...is useful for situations where the pthread library has been
// compiled with weak linkage for its interface symbols. This allows the
// threading support to be turned off by simply *not linking against
-lpthread*.
// In that situation, the value of *pthread_mutex_init* will be 0 and
// consequently pthread_enabled will be false. In such situations, all the
// ...
static const bool pthread_enabled = *true*;
But pthread_enabled has no relation with pthread_mutex_init. I've check
the log, pthread_enabled has been assigned to true since 2006. It was:
static const bool pthread_enabled = *static_cas...
2012 Jan 14
2
[LLVMdev] Unreachable code in Mutex.cpp
...; symbols in libc and strong definitions in libpthreads. The idea of this check is thus to detect if pthreads is linked into the app and enable threads if so.
Sorry, right - I should've been more clear. I understand that that's
what the declaration/boolean used to do:
static const bool pthread_enabled = static_cast<bool>(pthread_mutex_init);
But that's not what the code does now - the change you made 5 years
ago changed it to a constant:
static const bool pthread_enabled = true;
(I found this because the return outside the 'if (pthread_unabled) {
... return }' was mark...
2012 Jan 14
0
[LLVMdev] Unreachable code in Mutex.cpp
...definitions in libpthreads. The idea of this check is thus to detect if pthreads is linked into the app and enable threads if so.
>
> Sorry, right - I should've been more clear. I understand that that's
> what the declaration/boolean used to do:
>
>
> static const bool pthread_enabled = static_cast<bool>(pthread_mutex_init);
>
> But that's not what the code does now - the change you made 5 years
> ago changed it to a constant:
>
> static const bool pthread_enabled = true;
>
> (I found this because the return outside the 'if (pthread_una...
2012 Jan 14
0
[LLVMdev] Unreachable code in Mutex.cpp
On Jan 13, 2012, at 4:43 PM, David Blaikie wrote:
> It looks like for a while now (5 years) some code that was meant to do
> smart things in Mutex.cpp hasn't been doing such smart things:
>
> https://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/Mutex.cpp?r1=29287&r2=29932&diff_format=h
>
> I don't know if this change was even deliberate since it came in
2012 Jan 14
2
[LLVMdev] Unreachable code in Mutex.cpp
It looks like for a while now (5 years) some code that was meant to do
smart things in Mutex.cpp hasn't been doing such smart things:
https://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/Mutex.cpp?r1=29287&r2=29932&diff_format=h
I don't know if this change was even deliberate since it came in with
another change & the description doesn't mention it. Should we do
2012 Jan 15
1
[LLVMdev] Unreachable code in Mutex.cpp
...reads. The idea of this check is thus to detect if pthreads is linked into the app and enable threads if so.
>>
>> Sorry, right - I should've been more clear. I understand that that's
>> what the declaration/boolean used to do:
>>
>>
>> static const bool pthread_enabled = static_cast<bool>(pthread_mutex_init);
>>
>> But that's not what the code does now - the change you made 5 years
>> ago changed it to a constant:
>>
>> static const bool pthread_enabled = true;
>>
>> (I found this because the return outside...