search for: sanitizercommon

This morning I'm seeing 4 new sanitizer failures in SanitizerCommon-Unit (compared to a couple of days ago, when I didn't see these) - perhaps related to recent library refactoring? SanitizerCommon-Unit :: Sanitizer-i386-Test/DeadlockDetector.RemoveEdgesTest SanitizerCommon-Unit :: Sanitizer-i386-Test/SanitizerCommon.ThreadRegistryTest SanitizerCom...

Hi, I'm seeming new regressions form 4.0.0 for mips big endian: DataFlowSanitizer-mips64 :: custom.cc DataFlowSanitizer-mips64 :: propagate.c SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard.cc SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc San...

Hi all, I experienced some test failures under Linux, probably caused by r232936: In the test SanitizerCommon-Unit :: Sanitizer-i386-Test/MemoryMappingLayout.CodeRange the temporary test file was opened write-only, but was read from, what subsequently failed: Note: Google Test filter = MemoryMappingLayout.CodeRange [==========] Running 1 test from 1 test case. [----------] Global test environment set-up....

...ith-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-t...

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

Hello everyone, 9.0.0-rc5 was just tagged from the release_90 branch at r371837. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc5. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc5 Binaries will be added as they become available. There is only a single change from rc4 to rc5. Once more, the hope is that this will be the last release candidate and that we can

Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom

Hello again, 9.0.0-rc4 was just tagged from the release_90 branch at r371490. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc4. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc4 Binaries will be added as they become available. There are not a lot of changes from rc3 to rc4, and there are again no open release blockers, so I'm hoping this will be the last

Hi, I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload binaries. I've also updated the test-release.sh script to pull from GitHub instead of SVN, if you run into any issues with the new script, let me know. -Tom

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom

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

...r.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 &g...

Hello everyone, 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc6. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc6 This is the same as rc5 plus one very minor change (r371969) that still seemed good to pick up. I'm not allocating extra time for testing this one, expecting to tag

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

....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 :: Linux/signal_segv_handler.cc > SanitizerCommon-msan :: Posix/decorate_pro...

...zer.UnalignedStore16_precise2 MemorySanitizer-Unit :: Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore32 MemorySanitizer-Unit :: Msan-mips64-with-call-Test/MemorySanitizer.gethostbyname_r_erange MemorySanitizer-Unit :: Msan-mips64-with-call-Test/MemorySanitizer.ptrtoint SanitizerCommon-Unit :: Sanitizer-mips64-Test/SanitizerCommon.FileOps SanitizerCommon-Unit :: Sanitizer-mips64-Test/SanitizerIoctl.KVM_GET_LAPIC SanitizerCommon-Unit :: Sanitizer-mips64-Test/SanitizerIoctl.KVM_GET_MP_STATE SanitizerCommon-asan :: Linux/getpwnam_r_invalid_user.cc SanitizerCommon...

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

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