Displaying 4 results from an estimated 4 matches for "_glibcxx_has_gthreads".
2014 Jun 20
4
[LLVMdev] [PATCH] Replace the Execution Engine's mutex with std::recursive_mutex
...MinGW plus LLVM_ENABLE_THREADS would become unsupported.
Do people have objections to 2? I don't really like it either.
On Fri, Jun 20, 2014 at 10:33 AM, Yaron Keren <yaron.keren at gmail.com> wrote:
> The whole "mutex" and "shared_mutex" files are #ifdef
> _GLIBCXX_HAS_GTHREADS so if no _GLIBCXX_HAS_GTHREADS there are no mutexes
> and no call_once. thread lives in "thread" which is also #ifdef
> _GLIBCXX_HAS_GTHREADS.
> "condition_variable" and "future" are the same.
>
> I have tested gcc 4.8.2 predefines and _GLIBCXX_HAS_GTHRE...
2014 Jun 20
3
[LLVMdev] [PATCH] Replace the Execution Engine's mutex with std::recursive_mutex
...y, I mean only disable this for THREADS-WIN32, not threads-posix.
On Fri, Jun 20, 2014 at 11:14 AM, Zachary Turner <zturner at google.com> wrote:
> #2 is better if we can detect threads-win32 vs threads-posix on MinGW, and
> only disable this for threads-posix. We can check for
> _GLIBCXX_HAS_GTHREADS, but that seems somewhat hackish, so I wonder if
> there's a better way.
>
> To handle the switching, I guess we'll have to go back to the original
> option of having llvm::mutex, llvm::recursive_mutex, etc, and then
> conditionally typedefing them. Kinda sucks, but still be...
2014 Jun 20
3
[LLVMdev] [PATCH] Replace the Execution Engine's mutex with std::recursive_mutex
It sounds like this version of libstdc++ doesn't support
std::recursive_mutex from C++11. This is really unfortunate, because we
were hoping that moving to C++11 would allow us to use standard, portable
threading primitives.
Does this version of MinGW have any C++11 threading support? Is it just
recursive_mutex that is missing, or do we have to avoid std::mutex,
std::call_once, etc? lld
2014 Jun 20
3
[LLVMdev] [PATCH] Replace the Execution Engine's mutex with std::recursive_mutex
+llvmdev.
I find this pretty surprising. Actually, we already use std::mutex and
std::recursive_mutex in clang, lld, and other llvm projects, it's just a
coincidence that it hadn't been introduced into LLVM until my commits.
I'm not sure what the right thing to do here is. If I understand
correctly, it seems like in order to encounter this, a) you must be using
GCC, b) you must be