search for: memorysanit

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom

...nc > LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrier > LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrierArgs > LLVM-Unit :: Support/SupportTests/ThreadPoolTest.GetFuture > LLVM-Unit :: Support/SupportTests/ThreadPoolTest.PoolDestruction > MemorySanitizer :: Linux/obstack.cc > MemorySanitizer :: Linux/process_vm_readv.cc > MemorySanitizer :: fork.cc > MemorySanitizer :: iconv.cc > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.fgetgrent_r > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getg...

Dear testers, Release Candidate 3 has just been tagged [1]. Please build, test, and upload to the sftp. If there are no regressions from previous release candidates, this will be the last release candidate before the final release. Release notes can still go into the branch. Thanks again for all your work! Hans [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html

...been tagged [1]. Please build, test, and > upload to the sftp. Uploaded: clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Ubuntu 16.04 x86_64: Failing Tests (7): MemorySanitizer :: Linux/forkpty.cc MemorySanitizer :: Linux/tcgetattr.cc 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.getmntent...

...ustom.cc DataFlowSanitizer :: propagate.c LeakSanitizer-AddressSanitizer :: TestCases/swapcontext.cc LeakSanitizer-AddressSanitizer :: TestCases/use_registers.cc LeakSanitizer-Standalone :: TestCases/swapcontext.cc LeakSanitizer-Standalone :: TestCases/use_registers.cc MemorySanitizer :: Linux/process_vm_readv.cc MemorySanitizer :: allocator_mapping.cc MemorySanitizer :: dlerror.cc MemorySanitizer :: dtls_test.c MemorySanitizer :: memcmp_test.cc MemorySanitizer :: msan_print_shadow3.cc MemorySanitizer :: param_tls_limit.cc MemorySanitizer :...

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

...s, upload to the > sftp, and report results to this thread. LNT is looking good on Ubuntu 14.04 x64, uploaded: clang+llvm-3.7.0-rc2-x86_64-linux-gnu-ubuntu-14.04.tar.xz The errors reported during build are: 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/MemoryS...

...ineExecutionCounts.cpp LLVM :: tools/llvm-cov/showRegionMarkers.cpp LLVM :: tools/llvm-cov/showTemplateInstantiations.cpp LLVM :: tools/llvm-cov/universal-binary.c LLVM :: tools/llvm-cov/warnings.h These ^^ fail with "std::future_error / No associated state" as well. MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.fgetgrent_r MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent_r These don't confess why they failed in the log. MemorySanitizer-Unit :: Msan-x86_64-Test/M...

...LeakSanitizer-AddressSanitizer :: TestCases/swapcontext.cc > LeakSanitizer-AddressSanitizer :: TestCases/use_registers.cc > LeakSanitizer-Standalone :: TestCases/swapcontext.cc > LeakSanitizer-Standalone :: TestCases/use_registers.cc > MemorySanitizer :: Linux/process_vm_readv.cc > MemorySanitizer :: allocator_mapping.cc > MemorySanitizer :: dlerror.cc > MemorySanitizer :: dtls_test.c > MemorySanitizer :: memcmp_test.cc > MemorySanitizer :: msan_print_shadow3.cc >...

...s to this thread. >> > LNT is looking good on Ubuntu 14.04 x64, uploaded: > clang+llvm-3.7.0-rc2-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > The errors reported during build are: > > 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...

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release

Dear testers, 3.7.0-rc2 was just tagged. Please test, build binaries, upload to the sftp, and report results to this thread. A lot of fixes have been applied since rc1, both to the build script and the code in general, so hopefully it will be less bumpy this time. >From this point, I will no longer accept merge requests to finish existing features; it's now bug-fixes only. Thanks again

Hi, I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in -rc1 before I could send out a release announcement, so I decided to merge the fix and tag -rc2 to save some testing cycles. We can always use more testers, so if you are interested in helping, let me know. Thanks, Tom

(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There

...get one. Still not sure what caused > this. > > > > Thanks, > Hans > > > Appendix: compiler-rt test failures > =================================== > From Ben on Ubuntu 14.04 x64: > > 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 :: Ms...

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

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom

Hi all, MemorySanitizer (-fsanitize=memory flag) can now be used to build a self-hosted Clang. Several tests are still failing (most - due to bugs in the code), but the third-stage compiler is fully functional and passes the full test suite. Instructions are here: https://code.google.com/p/memory-sanitizer/wiki/Boots...

Hello everyone, 3.7-rc3 has just been tagged. Testers, please test, build binaries, upload to the sftp and report results to this thread. Again, a lot of patches got merged between rc2 and rc3, but hopefully nothing that should upset things. One thing that did change is that the release script now correctly symlinks clang-tools-extra into the build. If this causes problems on your platform,

Hi again, MemorySanitizer (msan) is now mature enough to bootstrap LLVM and run it w/o any additional tools. Msan has already found one bug in LLVM itself: http://llvm.org/bugs/show_bug.cgi?id=13929 Would anyone be willing to do a codereview (it was sent to llvm-commits: http://permalink.gmane.org/gmane.comp.compilers....