6.0.1-rc1 has been tagged

Hi,

I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading
binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do
so please try to do this before Friday, because I would like to tag 5.0.2-final then.

As a reminder to users and developers, May 18 is the deadline for submitting
merge requests for 6.0.1, so there is still time to get bug fixes in.

Thanks,
Tom

Will the PR’s marked as blockers of PR36649 be merged in or do we need to do something specific?

Will the PR's marked as blockers of PR36649 be merged in or do we need to do something specific?

Yes, I typically go through the list every few days to see if anything needs
to be done, and I will make sure everything is merged (if approved) before -rc2.
You can help by asking code owners for approval to merge changes so then I don't
have to.

-Tom

Windows is ready:

$ sha1sum LLVM-6.0.1-rc1-win*
ba11cad8bebd95a1d3c76769c6e4221d5e4b2d33 LLVM-6.0.1-rc1-win32.exe
95abb22a662c9360829aa5b66e853fcf8aeb8883 LLVM-6.0.1-rc1-win64.exe

Cheers,
Hans

works great on Debian!

Cheers,
S

Built for FreeBSD 10, tested and uploaded:

SHA256 (clang+llvm-6.0.1-rc1-amd64-unknown-freebsd10.tar.xz) = 8132159f133ffb593d56d47ecc408cf365853409cb8a148376d76e57daac4ad2
SHA256 (clang+llvm-6.0.1-rc1-i386-unknown-freebsd10.tar.xz) = 432fe4be6781ddf5bd5daa9ba7eb510edf2654ac0fecdbd91bc818d3a2789836

W dniu śro, 25.04.2018 o godzinie 21∶28 -0700, użytkownik Tom Stellard
via Release-testers napisał:

Hi,

I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading
binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do
so please try to do this before Friday, because I would like to tag 5.0.2-final then.

As a reminder to users and developers, May 18 is the deadline for submitting
merge requests for 6.0.1, so there is still time to get bug fixes in.

Looks regression-free on Gentoo. All green except for:

- the usual unsolved issue with LLDB, i.e.

  error: process launch failed: 'A' packet returned an error: -1

- 4 test failures on 32-bit x86 compiler-rt sanitizers:

  Failing Tests (4):
    LeakSanitizer-AddressSanitizer-i386 :: TestCases/large_allocation_leak.cc
    LeakSanitizer-AddressSanitizer-i386 :: TestCases/stale_stack_leak.cc
    LeakSanitizer-Standalone-i386 :: TestCases/large_allocation_leak.cc
    LeakSanitizer-Standalone-i386 :: TestCases/stale_stack_leak.cc

I'm going to see if it still happens with git master.

Hi Tom,

I've uploaded 6.0.1-rc1 binaries for Darwin x86_64.

- clang+llvm-6.0.1-rc1-x86_64-apple-darwin.tar.xz
- SHA 256: 29e8fbd195497f132ea70a0b4335be561585cce3332e5d032ce82221fb06b9cd

One change from the previous release is that these binaries were built with a minimum macOS deployment target of 10.9. This should address concerns about the macOS binaries requiring the latest OS.

Sorry for missing the thread about 5.0.2-rc1, I'll get to it today.

thanks,
vedant

Hi Tom,

MIPS looks ok here.

Binaries uploaded:
SHA256(clang+llvm-6.0.1-rc1-mipsel-linux-gnu.tar.xz)= 9059cc56630649cb07826aa50485c7698c641663ec257bec688765afdab1dac5
SHA256(clang+llvm-6.0.1-rc1-mips-linux-gnu.tar.xz)= 21feb3f5f6d5aa80639711b4d92dc1f5ed1ba99e6aaefbe0deeed220797a9447
SHA256(clang+llvm-6.0.1-rc1-x86_64-linux-gnu-debian8.tar.xz)= bf72feb64397b775e25caf24e948db209a6995bb9cae931ee887a839e7d4c88a

Thanks,
Simon

Forwarding to release-testers, I missed that my email client had stripped off the sender for reply-to-all.

Apologies for the noise.

Thanks,
Simon