search for: shared_futur

...n-sections -fdata-sections -O2 -g -DNDEBUG -fno-exceptions -o CMakeFiles/LLVMSupport.dir/ThreadPool.cpp.o -c /«PKGBUILDDIR»/lib/Support/ThreadPool.cpp In file included from /«PKGBUILDDIR»/lib/Support/ThreadPool.cpp:14:0: /«PKGBUILDDIR»/include/llvm/Support/ThreadPool.h: In member function 'std::shared_future<void> llvm::ThreadPool::async(Function&&, Args&& ...)': /«PKGBUILDDIR»/include/llvm/Support/ThreadPool.h:78:77: error: return type 'class std::shared_future<void>' is incomplete inline std::shared_future<VoidTy> async(Function &&F, Args &amp...

...the armel autobuilders now run on armv7 hardware and afaict Debian armel unlike raspbian doesn't have any contamination checking in place) but the build doesn't even get that far. It fails earlier with. > /«PKGBUILDDIR»/include/llvm/Support/ThreadPool.h: In member function 'std::shared_future<void> llvm::ThreadPool::async(Function&&, Args&& ...)': > /«PKGBUILDDIR»/include/llvm/Support/ThreadPool.h:77:77: error: return type 'class std::shared_future<void>' is incomplete > inline std::shared_future<VoidTy> async(Function&&amp...

...set_exception.pass.cpp (57866 of > 61786) > FAIL: libc++ :: > std/thread/futures/futures.promise/set_exception_at_thread_exit.pass.cpp > (57867 of 61786) > FAIL: libc++ :: std/thread/futures/futures.async/async.pass.cpp (57895 of 61786) > FAIL: libc++ :: std/thread/futures/futures.shared_future/get.pass.cpp > (57899 of 61786) > FAIL: libc++ :: > std/thread/futures/futures.task/futures.task.members/dtor.pass.cpp > (57902 of 61786) > FAIL: libc++ :: > std/thread/futures/futures.task/futures.task.members/make_ready_at_thread_exit.pass.cpp > (57913 of 61786) > FAIL: l...

...s.promise/set_value_at_thread_exit_void.pass.cpp libc++ :: std/thread/futures/futures.promise/set_value_const.pass.cpp libc++ :: std/thread/futures/futures.promise/set_value_void.pass.cpp libc++ :: std/thread/futures/futures.promise/swap.pass.cpp libc++ :: std/thread/futures/futures.shared_future/copy_assign.pass.cpp libc++ :: std/thread/futures/futures.shared_future/copy_ctor.pass.cpp libc++ :: std/thread/futures/futures.shared_future/ctor_future.pass.cpp libc++ :: std/thread/futures/futures.shared_future/dtor.pass.cpp libc++ :: std/thread/futures/futures.shared_future/get...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom

Hello everyone, It took a bit longer than planned due to master being a somewhat unstable at the branch point, but Release Candidate 1 has now been tagged as llvmorg-10.0.0-rc1. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc1 Pre-built binaries will be added there as they become available. Please file bug reports for any issues you find as blockers of

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom