[3.7 Release] RC4 has been tagged

Dear testers,

3.7.0-rc4 has just been tagged. It is identical to rc3, plus:

- r245902: Revert r245355: change of clang-tools-extra symlink in the
release script
- r245947: Merge of r245927: Fix LLDB build on MIPS
- r245948: Deprecate the DataLayout on the TargetMachine, and backport
the 3.8 API
- Changes to the ReleaseNotes.

Those changes should all be safe, and I expect this to be an extremely
short cycle.

Please build and test. If no new issues arise, I plan to tag this as
'final' tomorrow or Friday so we can ship the release next week.

Thanks,
Hans

Tests seem fine (except the usual sanitizer fails), uploaded: clang+llvm-3.7.0-rc4-x86_64-linux-gnu-ubuntu-14.04.tar.xz

Failing Tests (17):
     AddressSanitizer-x86_64-linux :: TestCases/Posix/readv.cc
     MemorySanitizer :: Linux/tcgetattr.cc
     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.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
     SanitizerCommon-asan :: Linux/getpass.cc
     SanitizerCommon-asan :: Posix/decorate_proc_maps.cc
     SanitizerCommon-lsan :: Linux/getpass.cc
     SanitizerCommon-msan :: Linux/getpass.cc
     SanitizerCommon-msan :: Posix/decorate_proc_maps.cc
     SanitizerCommon-tsan :: Linux/getpass.cc
     SanitizerCommon-tsan :: Posix/decorate_proc_maps.cc

   Expected Passes : 24041
   Expected Failures : 132
   Unsupported Tests : 377
   Unexpected Failures: 17
make[3]: *** [CMakeFiles/check-all] Error 1
make[3]: Target `CMakeFiles/check-all.dir/build' not remade because of errors.
make[2]: *** [CMakeFiles/check-all.dir/all] Error 2
make[1]: *** [CMakeFiles/check-all.dir/rule] Error 2
make[1]: Target `check-all' not remade because of errors.
make: *** [check-all] Error 2
[Release Phase3] check-all failed

# Comparing Phase 2 and Phase 3 files
### Testing Finished ###
### Package: clang+llvm-3.7.0-rc4-x86_64-linux-gnu-ubuntu-14.04.tar.xz
### Logs: /home/development/llvm/3.7.0/rc4/logs
### Errors:
[Release Phase3] check-all failed

Ben

Please build and test. If no new issues arise, I plan to tag this as
'final' tomorrow or Friday so we can ship the release next week.

I'm afraid I can't build and test that quickly with the equipment I have at the moment. The little endian build is running on machine that was designed to be a router and currently takes almost 24 hours due to lack of FPU, local disk, and RAM. The test-suite for this build used to take 3 days for the same reason (mostly the lack of FPU causing _massive_ numbers of kernel interrupts for FPU emulation) but I'm using a CI20 now that gets through it in a few hours thanks to its FPU.

Can you tag it on Monday instead?

Please build and test. If no new issues arise, I plan to tag this as
'final' tomorrow or Friday so we can ship the release next week.

I'm afraid I can't build and test that quickly with the equipment I have at the moment. The little endian build is running on machine that was designed to be a router and currently takes almost 24 hours due to lack of FPU, local disk, and RAM. The test-suite for this build used to take 3 days for the same reason (mostly the lack of FPU causing _massive_ numbers of kernel interrupts for FPU emulation) but I'm using a CI20 now that gets through it in a few hours thanks to its FPU.

Can you tag it on Monday instead?

Since RC3 built fine for you, there really shouldn't be anything in
RC4 that would cause problems. Maybe you could start a build to make
sure it seems OK, but we don't wait for all the bootstrapping and
test-suite to finish?

Ok. I'll get what I can done by the time you tag it and let you know if anything does cause problems.