search for: libwinpthread

...ng msys2. When I run `./configure` without any parameters and I still see missing pthreads impl. >> >> I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). >> >> mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >> MinGW-w64 winpthreads library >> mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >> MinGW-w64 winpthreads library >> msys/mingw-w64-cross-winpt...

Hi, I think I can at least answer why the Rust project prefers to use mingw-w64-win32threads: 1. It does not inject dependency on libwinpthread.dll, which is nice. 2. Those who tried building LLVM with mingw-w64-pthreads, had reported significant slowdown of the resulting Rust compiler (as compared to one linked to LLVM compiled with the win32threads flavor). Profiling seemed to point towards libpthreads' implementation of mutex. I...

...hreads vesion do not have? > > Yaron > > > 2014-09-25 9:52 GMT+03:00 Vadim Chugunov <vadimcn at gmail.com>: > >> Hi, >> I think I can at least answer why the Rust project prefers to use >> mingw-w64-win32threads: >> 1. It does not inject dependency on libwinpthread.dll, which is nice. >> 2. Those who tried building LLVM with mingw-w64-pthreads, had reported >> significant slowdown of the resulting Rust compiler (as compared to one >> linked to LLVM compiled with the win32threads flavor). Profiling seemed >> to point towards libpthrea...

Hi, I am trying to compile Libvirt from the source code on windows using msys2 but keep hitting issues while running `./configure`. …. > checking whether C compiler handles -Wno-suggest-attribute=pure… yes > checking whether C compiler handles -Wno-suggest-attribute=const... yes > checking for how to force completely read-only GOT table… > checking for how to avoid indirect lib

...ng-aarch64-libpsl 0.21.2-4 mingw-w64-clang-aarch64-libssh2 1.11.0-1 mingw-w64-clang-aarch64-libtasn1 4.19.0-1 mingw-w64-clang-aarch64-libtiff 4.5.1-2 mingw-w64-clang-aarch64-libunistring 1.1-1 mingw-w64-clang-aarch64-libunwind 16.0.5-1 mingw-w64-clang-aarch64-libwebp 1.3.1-1 mingw-w64-clang-aarch64-libwinpthread-git 11.0.0.r107.gd367cc9d7-1 mingw-w64-clang-aarch64-libxml2 2.11.4-2 mingw-w64-clang-aarch64-lld 16.0.5-3 mingw-w64-clang-aarch64-llvm 16.0.5-3 mingw-w64-clang-aarch64-llvm-libs 16.0.5-3 mingw-w64-clang-aarch64-make 4.4-2 mingw-w64-clang-aarch64-mlir 16.0.5-1 mingw-w64-clang-aarch64-nettle 3.9.1-1...

...> Yaron >> >> >> 2014-09-25 9:52 GMT+03:00 Vadim Chugunov <vadimcn at gmail.com>: >> >>> Hi, >>> I think I can at least answer why the Rust project prefers to use >>> mingw-w64-win32threads: >>> 1. It does not inject dependency on libwinpthread.dll, which is nice. >>> 2. Those who tried building LLVM with mingw-w64-pthreads, had reported >>> significant slowdown of the resulting Rust compiler (as compared to one >>> linked to LLVM compiled with the win32threads flavor). Profiling seemed >>> to point t...

...oolchain. 2014-09-24 9:06 GMT+03:00 Mueller-Roemer, Johannes Sebastian < Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de>: > I would love to see libc++ working on Windows. In any case, I personally > use MinGW with pthreads, as that supports std::thread etc. Yes, it uses > libwinpthread, but that shouldn't really be an issue. > > > > -- > > Johannes S. Mueller-Roemer, MSc > > Wiss. Mitarbeiter - Interactive Engineering Technologies (IET) > > > > Fraunhofer-Institut für Graphische Datenverarbeitung IGD > > Fraunhoferstr. 5 | 64283 Dar...

...; > I am using msys2. When I run `./configure` without any parameters and I still see missing pthreads impl. > > I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). > > mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > MinGW-w64 winpthreads library > mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > MinGW-w64 winpthreads library > msys/mingw-w64-cross-winpthreads-git 7.0...

...`./configure` without any parameters and I still see missing pthreads impl. > >> > >> I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). > >> > >> mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > >> MinGW-w64 winpthreads library > >> mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > >> MinGW-w64 winpthreads library > >> msys/m...

...e` without any parameters and I still see missing pthreads impl. >>>> >>>> I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). >>>> >>>> mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >>>> MinGW-w64 winpthreads library >>>> mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >>>> MinGW-w64 winpthreads library >>>&...

AKA: MinGW + win32threads is holding LLVM (and all of its subprojects) back. We need to stop supporting this host platform. I'm aware of essentially 2 reasonably important use cases for supporting MinGW + win32threads: 1) Sane host toolchain on Windows that doesn't require downloading MSVC. (I'm dubious about the value of this one...) 2) Cross-compiling a Windows clang.exe (and

+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