Tom Stellard via llvm-dev
2021-May-26 07:15 UTC
[llvm-dev] 12.0.1-rc1 release has been tagged
Hi, I've tagged the 12.0.1-rc1 release. Testers may upload binaries and report results. -Tom
Hans Wennborg via llvm-dev
2021-May-26 15:42 UTC
[llvm-dev] [Release-testers] 12.0.1-rc1 release has been tagged
Windows looks good. The binaries are ready: $ sha256sum LLVM-12.0.1-rc1-win*.exe dc4ef18dc971a2ced2f42184da7de99eece7fe50863918f50588834f1612870d LLVM-12.0.1-rc1-win32.exe 39c35b4e2c737f4788474d17559fb8aa05cd3e2f613653ef759913a5e61a9a48 LLVM-12.0.1-rc1-win64.exe Built with the attached script as usual. On Wed, May 26, 2021 at 9:15 AM Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote:> Hi, > > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and > report results. > > -Tom > > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210526/e009be15/attachment.html>
Neil Nelson via llvm-dev
2021-May-26 18:22 UTC
[llvm-dev] 12.0.1-rc1 release has been tagged
Uploaded Ubuntu 21.04 with lldb. sha256sum clang+llvm-12.0.1-rc1-x86_64-linux-gnu-ubuntu-21.04.tar.xz e9d9dcf92870bfd52dc10dd34c4a04a6f6a188d0d396d7f996638d3c1456bb39 Failed Tests (15): MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.fstatat MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.stat MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.fstatat MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.stat MemorySanitizer-X86_64 :: fstat.cpp MemorySanitizer-lld-X86_64 :: fstat.cpp SanitizerCommon-asan-i386-Linux :: Linux/crypt_r.cpp SanitizerCommon-asan-i386-Linux :: Posix/crypt.cpp SanitizerCommon-lsan-i386-Linux :: Linux/crypt_r.cpp SanitizerCommon-lsan-i386-Linux :: Posix/crypt.cpp SanitizerCommon-msan-x86_64-Linux :: Posix/lstat.cpp SanitizerCommon-ubsan-i386-Linux :: Linux/crypt_r.cpp SanitizerCommon-ubsan-i386-Linux :: Posix/crypt.cpp libarcher :: races/lock-unrelated.c lldb-api :: tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py Testing Time: 538.78s Unsupported : 3416 Passed : 84233 Expectedly Failed: 267 Failed : 15 Submitted blocker bugs 50487 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.fstatat' FAILED 50488 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.stat' FAILED 50489 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.fstatat' FAILED 50490 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.stat' FAILED 50491 - TEST 'MemorySanitizer-X86_64 :: fstat.cpp' FAILED 50492 - TEST 'MemorySanitizer-lld-X86_64 :: fstat.cpp' FAILED 50493 - TEST 'libarcher :: races/lock-unrelated.c' FAILED Not saying these bugs should be blockers. Only that it seems the place to put them. Other fails in prior bugs. 48946 - skipping incompatible /usr/lib/x86_64-linux-gnu/libcrypt.so when searching for -lcrypt 48960 - FAIL: lldb-api :: tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py llvm-test-suite Passed: 2405 Tests: 2825 Metric: exec_time Program 12.0.0-rc5 12.0.1-rc1 diff test-suite.../GCC-C-execute-20030120-1.test 0.00 0.00 inf% test-suite...d_ops_test_op_pmulhuw_134.test 0.00 0.00 inf% test-suite...d_ops_test_op_pmulhuw_181.test 0.00 0.01 inf% test-suite...d_ops_test_op_pmulhuw_182.test 0.00 0.00 inf% test-suite.../GCC-C-execute-20170419-1.test 0.00 0.00 inf% test-suite.../GCC-C-execute-20171008-1.test 0.00 0.00 inf% test-suite.../GCC-C-execute-20180112-1.test 0.00 0.00 inf% test-suite.../GCC-C-execute-20180131-1.test 0.00 0.00 inf% test-suite...te/GCC-C-execute-920625-1.test 0.00 0.00 inf% test-suite...te/GCC-C-execute-920721-1.test 0.00 0.00 inf% test-suite...md_ops_test_op_pmulhw_107.test 0.00 0.00 inf% test-suite...te/GCC-C-execute-920731-1.test 0.00 0.00 inf% test-suite...imd_ops_test_op_pmulhw_11.test 0.00 0.00 inf% test-suite...te/GCC-C-execute-921204-1.test 0.00 0.00 inf% test-suite...ute/GCC-C-execute-pr69447.test 0.00 0.00 inf% Geomean difference nan% 12.0.0-rc5 12.0.1-rc1 diff count 2807.000000 2807.000000 2784.000000 mean 210.572082 223.561162 inf std 2830.933581 2825.553821 NaN min 0.000000 0.000000 -1.000000 25% 0.000400 0.000400 -0.200000 50% 0.000500 0.000500 0.000000 75% 0.012950 0.011150 0.135624 max 79285.584375 85835.460625 inf Neil Nelson On 5/26/21 1:15 AM, Tom Stellard via llvm-dev wrote:> Hi, > > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and > report results. > > -Tom > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210526/cfed7d0a/attachment.html>
Dimitry Andric via llvm-dev
2021-May-28 20:24 UTC
[llvm-dev] [Release-testers] 12.0.1-rc1 release has been tagged
On 26 May 2021, at 09:15, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote:> > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and report results.For 12.0.1 rc1, I have built and tested on both FreeBSD 11 and 12. No additional patches were needed. Main results on amd64-freebsd11: Unsupported : 5562 (12.0.0 final: 5562) Passed : 80189 (12.0.0 final: 80179) Expectedly Failed : 247 (12.0.0 final: 247) Timed Out : 2 (12.0.0 final: 2) Failed : 97 (12.0.0 final: 96) Unexpectedly Passed: 2 (12.0.0 final: 2) Test suite results on amd64-freebsd11: Passed: 2399 (12.0.0 final: 2399) Failed: 3 (12.0.0 final: 3) Main results on amd64-freebsd12: Unsupported : 5562 (12.0.0 final: 5562) Passed : 80194 (12.0.0 final: 80181) Expectedly Failed : 243 (12.0.0 final: 243) Timed Out : 2 (12.0.0 final: 3) Failed : 92 (12.0.0 final: 93) Unexpectedly Passed: 6 (12.0.0 final: 6) Test suite results on amd64-freebsd12: Passed: 2399 (12.0.0 final: 2399) Failed: 3 (12.0.0 final: 3) Main results on i386-freebsd11: Unsupported : 3976 (12.0.0 final: 3976) Passed : 76736 (12.0.0 final: 76723) Expectedly Failed : 224 (12.0.0 final: 224) Failed : 53 (12.0.0 final: 55) Unexpectedly Passed: 1 (12.0.0 final: 1) Main results on i386-freebsd12: Unsupported : 3976 (12.0.0 final: 3976) Passed : 76739 (12.0.0 final: 76725) Expectedly Failed : 222 (12.0.0 final: 222) Failed : 50 (12.0.0 final: 53) Unexpectedly Passed: 3 (12.0.0 final: 3) Uploaded: SHA256 (clang+llvm-12.0.1-rc1-amd64-unknown-freebsd11.tar.xz) = 68ccfa684f181d69adc581c28cbc1d52a12396c444d3ba3543e99eb6e8b94d14 SHA256 (clang+llvm-12.0.1-rc1-amd64-unknown-freebsd12.tar.xz) = 6847c90d33eb8a597b372706fa1a9b6dac3ebcaffcd0b956287d0ac173ec8c50 SHA256 (clang+llvm-12.0.1-rc1-i386-unknown-freebsd11.tar.xz) = 7335ab91bfdab488071527345b4c5066544b34a0a11efd31f49ecf01ac08b096 SHA256 (clang+llvm-12.0.1-rc1-i386-unknown-freebsd12.tar.xz) = a20428ff308583f9d44f3f4eb86b720f3cd319592eb7805b54973f7b886cf862 -Dimitry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 223 bytes Desc: Message signed with OpenPGP URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210528/bbb3c319/attachment.sig>
Michał Górny via llvm-dev
2021-May-28 20:45 UTC
[llvm-dev] [Release-testers] 12.0.1-rc1 release has been tagged
On Wed, 2021-05-26 at 00:15 -0700, Tom Stellard via Release-testers wrote:> Hi, > > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and report results. >I've started testing, hit two bugs I've already reported for 12.0.0 RCs and figured out I'm wasting my time. It seems that LLVM reached the point where releases are pushed through just for the sake of releases and QA doesn't exist. -- Best regards, Michał Górny
Tom Stellard via llvm-dev
2021-Jun-01 17:03 UTC
[llvm-dev] [Release-testers] 12.0.1-rc1 release has been tagged
On 5/28/21 1:45 PM, Michał Górny wrote:> On Wed, 2021-05-26 at 00:15 -0700, Tom Stellard via Release-testers > wrote: >> Hi, >> >> I've tagged the 12.0.1-rc1 release. Testers may upload binaries and report results. >> > > I've started testing, hit two bugs I've already reported for 12.0.0 RCs > and figured out I'm wasting my time. It seems that LLVM reached > the point where releases are pushed through just for the sake of > releases and QA doesn't exist. >Which bugs are these? -Tom
Albion Fung via llvm-dev
2021-Jun-02 14:35 UTC
[llvm-dev] [Release-testers] 12.0.1-rc1 release has been tagged
Hello, SHA1s: Ubuntu: 229052e7ad72b9f8ad4b8d1a5c489a3a8c01a80a RHEL: fc29b460ec5e1645819f5215d35e6d4fd4ff1ad3 On Wed, 26 May 2021 at 03:15, Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote:> Hi, > > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and > report results. > > -Tom > > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210602/34733012/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-12.0.1-rc1-powerpc64le-linux-ubuntu-18.04.sha1 Type: application/octet-stream Size: 102 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210602/34733012/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-12.0.1-rc1-powerpc64le-linux-rhel-7.4.sha1 Type: application/octet-stream Size: 98 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210602/34733012/attachment-0001.obj>
Albion Fung via llvm-dev
2021-Jun-02 14:37 UTC
[llvm-dev] [Release-testers] 12.0.1-rc1 release has been tagged
Hello, Sorry, to clarify - SHA1 for PowerPC8: RHEL: fc29b460ec5e1645819f5215d35e6d4fd4ff1ad3 Ubuntu: 229052e7ad72b9f8ad4b8d1a5c489a3a8c01a80a Albion On Wed, 26 May 2021 at 03:15, Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote:> Hi, > > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and > report results. > > -Tom > > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210602/eb7a21e0/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-12.0.1-rc1-powerpc64le-linux-rhel-7.4.sha1 Type: application/octet-stream Size: 98 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210602/eb7a21e0/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-12.0.1-rc1-powerpc64le-linux-ubuntu-18.04.sha1 Type: application/octet-stream Size: 102 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210602/eb7a21e0/attachment-0001.obj>
Chandler Carruth via llvm-dev
2021-Jun-04 07:00 UTC
[llvm-dev] 12.0.1-rc1 release has been tagged
In addition to the issues mentioned in this thread, I'd also like to ask if it would be possible to fix these two bugs as well: https://bugs.llvm.org/show_bug.cgi?id=43604 (maybe unique to Debian packages) https://bugs.llvm.org/show_bug.cgi?id=46321 Both of these are fixable exclusively by passing flags to CMake during the build, no source changes are needed here. Homebrew packages for Linux have fixed them now, but it'd be really great for the Linux distribution packages to have these fixes too. I believe the only thing needed is to add the following to the `RUNTIMES_CMAKE_ARGS` list: -DCMAKE_POSITION_INDEPENDENT_CODE=ON -DLIBCXX_ENABLE_STATIC_ABI_LIBRARY=ON -DLIBCXX_STATICALLY_LINK_ABI_IN_SHARED_LIBRARY=OFF -DLIBCXX_STATICALLY_LINK_ABI_IN_STATIC_LIBRARY=ON -DLIBCXX_USE_COMPILER_RT=ON -DLIBCXXABI_USE_COMPILER_RT=ON -DLIBCXXABI_USE_LLVM_UNWINDER=ON (Technically, the last three are not strictly necessary, but without them the installed libc++ and libc++abi libraries may fail due to missing features in libgcc_s on some Linux platforms and it seems both easy and beneficial to avoid this.) On Wed, May 26, 2021 at 12:15 AM Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Hi, > > I've tagged the 12.0.1-rc1 release. Testers may upload binaries and > report results. > > -Tom > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210604/090a2286/attachment-0001.html>