search for: libunwind_has_pthread_lib

Displaying 3 results from an estimated 3 matches for "libunwind_has_pthread_lib".

Unifying CMake variable names used in checks across subprojects
2020 Sep 22
2
Unifying CMake variable names used in checks across subprojects
...he problem is that in LLVM, each subproject uses different variable names for results of these checks. For example, most subprojects check if pthread is available and store the result in: COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) LIBCXX_HAS_PTHREAD_LIB (libc++) LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) LIBUNWIND_HAS_PTHREAD_LIB (libunwind) HAVE_LIBPTHREAD (llvm) This means that even though this check would ideally be performed just once (per target) and reused everywhere, it's performed 5 times. The same is true for most flags and library checks. I think that this is really unnecessary and could be easily improved b...
Unifying CMake variable names used in checks across subprojects
2020 Sep 22
2
Unifying CMake variable names used in checks across subprojects
...M, each subproject uses different variable names for results of these checks. For example, most subprojects check if pthread is available and store the result in: > > COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) > LIBCXX_HAS_PTHREAD_LIB (libc++) > LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) > LIBUNWIND_HAS_PTHREAD_LIB (libunwind) > HAVE_LIBPTHREAD (llvm) > > This means that even though this check would ideally be performed just once (per target) and reused everywhere, it's performed 5 times. The same is true for most flags and library checks. > > I think that this is really unnecessary and c...
Unifying CMake variable names used in checks across subprojects
2020 Sep 25
2
Unifying CMake variable names used in checks across subprojects
...ses different variable names for results of these checks. For example, most subprojects check if pthread is available and store the result in: >> >> COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) >> LIBCXX_HAS_PTHREAD_LIB (libc++) >> LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) >> LIBUNWIND_HAS_PTHREAD_LIB (libunwind) >> HAVE_LIBPTHREAD (llvm) >> >> This means that even though this check would ideally be performed just once (per target) and reused everywhere, it's performed 5 times. The same is true for most flags and library checks. >> >> I think that this is real...