On 2 March 2017 at 19:47, Hans Wennborg via Release-testers <release-test...@lists.llvm.org> wrote: > Hello testers, > > 4.0.0-rc3 was just tagged from the branch at r296762.
ARM looks good, bd3c31f080a016409179fa8cb69da4e2fa14c951 clang+llvm-4.0.0-rc3-armv7a-linux-gnueabihf.tar.xz AArch64 has a libc++ error we did not see on RC2: libc++ :: std/thread/thread.condition/thread.condition.condvarany/wait_for.pass.cpp wait_for.pass.cpp.exe: /home/renato.golin/devel/llvm/release/rc3/llvm.src/projects/libcxx/test/std/thread/thread.condition/thread.condition.condvarany/wait_for.pass.cpp:58: void f(): Assertion `t1 - t0 - milliseconds(250) < milliseconds(50)' failed. Copying Eric and Marshall to see if they know of any back-ported commit that could cause this or if that's just the test's own instability (which seems to be the case). Anyway, binaries uploaded: 9356d607c68fbf8de56c03bde70c2964a794d26e clang+llvm-4.0.0-rc3-aarch64-linux-gnu.tar.xz > This is a release candidate in the real sense: if no major issues show > up with this one, it is the version that will be released. There is one rename that will land on trunk that needs to be announced on 4.0's release notes (https://reviews.llvm.org/D30510), but this won't need a new re-spin, just an update on the release notes before the final tag. cheers, --renato _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
