[LLVMdev] [3.7 Release] We have branched (original) (raw)

Daniel Sanders Daniel.Sanders at imgtec.com
Thu Jul 16 03:09:43 PDT 2015

Test-release.sh is giving 'make check-all' failures I didn't used to have but there all (except one) for projects we didn't build in 3.6.2 so that's not a big problem.

The failures are: AddressSanitizer-mips-linux :: TestCases/Linux/kernel-area.cc AddressSanitizer-mips-linux :: TestCases/Posix/coverage-direct-large.cc Clang :: Driver/cuda-options.cu UBSan-ASan-mips :: TestCases/Float/cast-overflow.cpp UBSan-Standalone-mips :: TestCases/Float/cast-overflow.cpp libc++abi :: backtrace_test.pass.cpp libc++abi :: test_demangle.pass.cpp I had to kill an excessively long 'llc -march=r600 -mcpu=cypress' process (>500 minutes) to make the tests finish. I assume it's one of those failures.

Tom: Are you aware of any r600 tests that run forever?

Sagar: Could you look into the two ubsan failures? Kumar: Could you look into the two asan failures? The test system is running 32-bit Debian Jessie for mips (big-endian) and is a MIPS64r2 CPU. You'll need to configure llvm with -DLLVM_HOST_TRIPLE=mips-linux-gnu.

-----Original Message----- From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] On Behalf Of Daniel Sanders Sent: 15 July 2015 11:26 To: Hans Wennborg; llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu Subject: Re: [cfe-dev] [LLVMdev] [3.7 Release] We have branched

Hi, I see there's no rc1 tag yet so I'll try the branch directly with D10715 (switch to cmake) and D6563 (enables directly testing branch with test-release.sh) applied. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-_ _bounces at cs.uiuc.edu] > On Behalf Of Hans Wennborg > Sent: 15 July 2015 01:25 > To: llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > Subject: [LLVMdev] [3.7 Release] We have branched > > Hi all, > > The 3.7 release branch was created from trunk at r242221 today (around > 10:40 pm UTC). > > Branch policy: > > - Any doc changes can go in. Updates to the release notes are highly > encouraged, and should be committed directly to the branch. > > - All other patches should be approved by the release manager (me) and > the appropriate code owner. To get a change merged, commit it to > trunk, and then reply to the commit email with myself and the code > owner cc'd, asking for approval. > > - Fixes to complete existing features may be merged. However, the > features must be completed before Phase II of testing starts, > otherwise they should be disabled. If you recently committed something > experimental to trunk, please make sure it's disabled on the branch. > > - For any bug fixes that you think might apply to the release branch, > please cc me on the commit message. > > Cheers, > Hans _> ________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

cfe-dev mailing list cfe-dev at cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

More information about the llvm-dev mailing list