search for: compiler_builtins

...sure how it ever worked before, but I need to merge > r220117 to make it work. > > I also got two test failures. I haven't checked yet if they also occur > in 3.5, but I'm not sure they matter on Windows: > > LLVM: CodeGen/Mips/cconv/arguments-struct.ll > Clang: Modules/compiler_builtins.m > > I've uploaded it to the sftp: > LLVM-3.5.1-rc1-win32.exe > sha1: 3c3892daa5119e60ee7b0917c4c1ac8251a949c6 > > - Hans > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141213/4f...

...gin. Remember to use the 3.5 > branch of the test-suite. If you have any questions, let me know. I've uploaded the Windows installer to the sftp with sha1: b56681a457954916ac9c8f0d36426cde0a21ee1d LLVM-3.5.1-rc2-win32.exe Build worked fine this time. The only failing lit test is Modules/compiler_builtins.m, which I guess is PR20995. That's probably not cause for concern, but maybe we should remove the test from the branch for those who build from source? CC'ing Yaron who has looked at the PR some. - Hans _______________________________________________ LLVM Developers mailing list LLVMdev...

Hi, I've just tagged 3.5.1-rc2, so testing can begin. Remember to use the 3.5 branch of the test-suite. If you have any questions, let me know. -Tom

Hi, 3.5.1-rc1 has been tagged, so it is time to begin testing. We can always use more testers, so if you would like to volunteer, let me know. For those that are new to testing, please review the documentation for how validate a new release: http://llvm.org/docs/ReleaseProcess.html Remember that when we check for regressions we want to compare the test results of 3.5.1-rc1 with 3.5.0-final.

...> branch of the test-suite. If you have any questions, let me know. > > I've uploaded the Windows installer to the sftp with sha1: > b56681a457954916ac9c8f0d36426cde0a21ee1d LLVM-3.5.1-rc2-win32.exe > > Build worked fine this time. The only failing lit test is > Modules/compiler_builtins.m, which I guess is PR20995. That's probably > not cause for concern, but maybe we should remove the test from the > branch for those who build from source? CC'ing Yaron who has looked at > the PR some. > > - Hans > _______________________________________________ > LL...

Hi testers! 3.6.0-rc1 was just tagged, so testing can begin. I'm not super familiar with the testing script yet, but I believe the idea is to run it as follows: $ utils/release/test-release.sh -release 3.6.0 -rc 1 -triple x86_64-unknown-linux-gnu With the -triple value substituted for your platform. Bill's 3.5rc1 email also said 'test-suite' needs to be run by hand. Please

...get/Sparc/MCTargetDesc/CMakeFiles 7.9M build/lib/Target/Sparc/MCTargetDesc 7.8M build/tools/lli/ChildTarget/CMakeFiles/lli-child-target.dir 7.8M build/tools/lli/ChildTarget/CMakeFiles 7.8M build/tools/lli/ChildTarget 7.8M build/tools/llc/CMakeFiles/llc.dir 7.7M build/tools/clang/test/Modules/Output/compiler_builtins.m.tmp 7.6M build/tools/clang/tools/clang-check/CMakeFiles/clang-check.dir 7.6M build/tools/clang/tools/clang-check/CMakeFiles 7.6M build/tools/clang/tools/clang-check 7.5M build/tools/clang/test/Analysis/Output 7.4M build/tools/clang/tools/clang-fuzzer/handle-cxx/CMakeFiles 7.4M build/tools/clang/t...