Hello testers,
4.0.0-rc3 was just tagged from the branch at r296762.
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.
Please let me know if you find any issues, including in release notes
or documentation, which will be on the pre-release web site later
today.
Please build, test, and upload binaries to the sftp and I'll publish
them when they're ready.
Many thanks, we're almost there!
Cheers,
Hans
Pushed:
9bdd5788761d0b02cdc84104aafd6b0e835a2fc0 rc3/clang+llvm-4.0.0-rc3-x86_64-apple-darwin.tar.xz
I didn't have a great deal of luck this time round. I was trying to build with lldb in a chroot, but it was having none of it, the tests didn't complete and there were quite a few readline failures (I think it was lack of access to a TTY). Pretty sure this was the case for rc2 as well, which is why I didn't manage to get a build out, apologies for that.
I've pushed clang+llvm-4.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
I should be able to get a build for x86_64-linux-gnu-ubuntu-16.10 in the next couple of days.
This jumped out at me:
# Comparing Phase 2 and Phase 3 files
file scudo_utils.cpp.o differs between phase 2 and phase 3
Without lldb, these are the complete results:
Failing Tests (32):
AddressSanitizer-x86_64-linux :: TestCases/Posix/readv.cc
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getaddrinfo
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyaddr
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyaddr_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname2
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname2_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname_r_erange
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getaddrinfo
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyaddr
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyaddr_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname2
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname2_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname_r_erange
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostent
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostent_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent_r
MemorySanitizer-x86_64 :: Linux/forkpty.cc
MemorySanitizer-x86_64 :: Linux/tcgetattr.cc
MemorySanitizer-x86_64 :: getaddrinfo-positive.cc
SanitizerCommon-asan-x86_64-Linux :: Posix/getpass.cc
SanitizerCommon-lsan-x86_64-Linux :: Posix/getpass.cc
SanitizerCommon-msan-x86_64-Linux :: Posix/getpass.cc
SanitizerCommon-tsan-x86_64-Linux :: Posix/getpass.cc
Expected Passes : 38132
Expected Failures : 220
Unsupported Tests : 1049
Unexpected Failures: 32
CMakeFiles/check-all.dir/build.make:57: recipe for target 'CMakeFiles/check-all' failed
make[3]: *** [CMakeFiles/check-all] Error 1
make[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of errors.
CMakeFiles/Makefile2:174: recipe for target 'CMakeFiles/check-all.dir/all' failed
make[2]: *** [CMakeFiles/check-all.dir/all] Error 2
CMakeFiles/Makefile2:181: recipe for target 'CMakeFiles/check-all.dir/rule' failed
make[1]: *** [CMakeFiles/check-all.dir/rule] Error 2
make[1]: Target 'check-all' not remade because of errors.
Makefile:184: recipe for target 'check-all' failed
make: *** [check-all] Error 2
[Release Phase3] check-all failed
# Comparing Phase 2 and Phase 3 files
file scudo_utils.cpp.o differs between phase 2 and phase 3
### Testing Finished ###
### Package: clang+llvm-4.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
### Logs: /scratch/llvm/clang-4/rc3/logs
### Errors:
[Release Phase3] check-all failed
Ben
Windows:
$ sha256sum *4.0.0-rc3*.exe
77a228b0ae0aaa7b806630b1f4935636fb25299fe32cdd943d2efeb96f64db78
LLVM-4.0.0-rc3-win32.exe
38debee5ae5e2eacec0ed0012b78aa272abba009733f429c2d71bfa21f8da767
LLVM-4.0.0-rc3-win64.exe
Built by the attached batch file.
build_llvm_400.bat|attachment (3.76 KB)
Hi,
OpenMandriva Cooker is updated on all architectures, no failures detected.
Also launched a successful build of AOSP master on Hikey (aarch64) with 4.0-rc3 (in this build, even the kernel is built with clang).
ttyl
bero
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 (⚙ D30510 Vulcan is now ThunderX2T99), but this
won't need a new re-spin, just an update on the release notes before
the final tag.
cheers,
--renato
Built and tested as expected on FreeBSD 10. I have uploaded the following:
SHA256 (clang+llvm-4.0.0-rc3-amd64-unknown-freebsd10.tar.xz) = 95d0ad58d546e15f6bb3f275840c774311e05268f9fa45fd5b460f4dea7e91ce
SHA256 (clang+llvm-4.0.0-rc3-i386-unknown-freebsd10.tar.xz) = 1b160ea41da08f6605b212a6cbf9b3fa373623c5dde54a04d20a5398a1548122
In other news, I have imported branches/release_40 r296509 (almost identical to this rc3) into FreeBSD 12-CURRENT yesterday:
https://svnweb.freebsd.org/changeset/base/314564
This also includes lld, and an option to link the FreeBSD base system with it.
-Dimitry
Uploaded in Debian. Works great!
Thanks,
Sylvestre
> 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.xzAArch64 has a libc++ error we did not see on RC2:
libc++ :: std/thread/thread.condition/thread.condition.condvarany/wait
_for.pass.cppwait_for.pass.cpp.exe:
/home/renato.golin/devel/llvm/release/rc3/llvm.src/projects/
libcxx/test/std/thread/thread.condition/thread.condition.con
dvarany/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).
Nothing relevant to this test has changed since the initial 4.0 branch. I
think it's safe to assume
the test is flakey, (Although I've never seen this specific test timeout
before)
Unfortunately I got reports of some source files resulting in excessive compile times, which was apparently caused by r287232:
https://bugs.llvm.org/show_bug.cgi?id=32142
I will most likely reverted r287232 locally, but it would be good to have some more eyes (and test cases) on that commit...
-Dimitry
Pushed clang+llvm-4.0.0-rc3-x86_64-linux-gnu-ubuntu-16.10.tar.xz
Failing Tests (34):
AddressSanitizer-x86_64-linux :: TestCases/Posix/readv.cc
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getaddrinfo
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyaddr
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyaddr_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname2
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname2_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname_r_erange
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getaddrinfo
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyaddr
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyaddr_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname2
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname2_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostbyname_r_erange
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostent
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostent_r
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent
MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent_r
MemorySanitizer-x86_64 :: Linux/forkpty.cc
MemorySanitizer-x86_64 :: Linux/tcgetattr.cc
MemorySanitizer-x86_64 :: getaddrinfo-positive.cc
SanitizerCommon-asan-x86_64-Linux :: Posix/getpass.cc
SanitizerCommon-lsan-x86_64-Linux :: Posix/getpass.cc
SanitizerCommon-msan-x86_64-Linux :: Posix/getpass.cc
SanitizerCommon-tsan-x86_64-Linux :: Posix/getpass.cc
ThreadSanitizer-x86_64 :: Linux/user_malloc.cc
libc++ :: std/localization/locales/locale/locale.cons/char_pointer.pass.cpp
Expected Passes : 38130
Expected Failures : 220
Unsupported Tests : 1049
Unexpected Failures: 34
CMakeFiles/check-all.dir/build.make:57: recipe for target 'CMakeFiles/check-all' failed
make[3]: *** [CMakeFiles/check-all] Error 1
make[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of errors.
CMakeFiles/Makefile2:174: recipe for target 'CMakeFiles/check-all.dir/all' failed
make[2]: *** [CMakeFiles/check-all.dir/all] Error 2
CMakeFiles/Makefile2:181: recipe for target 'CMakeFiles/check-all.dir/rule' failed
make[1]: *** [CMakeFiles/check-all.dir/rule] Error 2
make[1]: Target 'check-all' not remade because of errors.
Makefile:184: recipe for target 'check-all' failed
make: *** [check-all] Error 2
[Release Phase3] check-all failed
# Comparing Phase 2 and Phase 3 files
file scudo_utils.cpp.o differs between phase 2 and phase 3
### Testing Finished ###
### Package: clang+llvm-4.0.0-rc3-x86_64-linux-gnu-ubuntu-16.10.tar.xz
### Logs: /scratch/llvm/clang-4/yakkety/rc3/logs
### Errors:
[Release Phase3] check-all failed
Ben
I have pushed rc3 binaries.
0bcfd7061b7ae271f8a9aa45bd005c1b clang+llvm-4.0.0-rc3-mipsel-linux-gnu.tar.xz
01d8bb5409831fb8cdb3caa3b831e29b clang+llvm-4.0.0-rc3-mips-linux-gnu.tar.xz
e3e1acc5823371590d1f8f1d55dc915b clang+llvm-4.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz
Looks ok to me.
I'll fire up testing for rc4.
Thanks,
Simon
W dniu 02.03.2017, czw o godzinie 11∶47 -0800, użytkownik Hans Wennborg
via llvm-dev napisał:
Hello testers,
4.0.0-rc3 was just tagged from the branch at r296762.
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.Please let me know if you find any issues, including in release notes
or documentation, which will be on the pre-release web site later
today.Please build, test, and upload binaries to the sftp and I'll publish
them when they're ready.Many thanks, we're almost there!
Just a quick note that on Gentoo end this RC looks real good. I had to
backport/add a few more patches, and with them we have 100% tests
passing on amd64 & x86. Hopefully we'll get them all in for 5.0.0.
Thanks a lot!
I probably won't be able to make it for rc4 but it doesn't look like
it's going to break anything specific to us.