Hans Wennborg via llvm-dev
2020-Mar-19 13:51 UTC
[llvm-dev] [10.0.0 Release] Release Candidate 5 is here
Hello again, I had hoped that rc4 would be the last one, but I wanted to pick up one more fix, so here we go. Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the release branch at 35627038123. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 If nothing new comes up, I plan to tag 'final' on Monday. Testers, if you still have cycles, please take this for a quick spin. Thanks, Hans
Hans Wennborg via llvm-dev
2020-Mar-19 14:10 UTC
[llvm-dev] [10.0.0 Release] Release Candidate 5 is here
On Thu, Mar 19, 2020 at 2:51 PM Hans Wennborg <hans at chromium.org> wrote:> > Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go.I should have included this in the previous mail: the fix was for https://llvm.org/PR45206 and I also picked up the fix for https://llvm.org/PR45162 which seemed low-risk.
Bernhard Rosenkraenzer via llvm-dev
2020-Mar-19 16:25 UTC
[llvm-dev] ?==?utf-8?q? [Release-testers] [10.0.0?==?utf-8?q? Release] Release Candidate 5 is here
Hi, we've updated OpenMandriva, and started a mass build. Looks good so far, except we found 1 more bug (not a regression from previous RCs, but newly exposed by a package update introducing code that triggers it). https://bugs.llvm.org/show_bug.cgi?id=45251 I don't think this is an extremely serious bug (takes a few not too common constructs to trigger it), but still would be nice to fix given a lot of users will likely run into it (we can't be the only distro that ships libtorrent-rasterbar). ttyl bero On Thursday, March 19, 2020 14:51 CET, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:> Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. > > Source code and docs are available at > https://prereleases.llvm.org/10.0.0/#rc5 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin. > > Thanks, > Hans > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
Tobias Hieta via llvm-dev
2020-Mar-19 19:51 UTC
[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 5 is here
Hello, macOS builds are up, sha256: e375ea7101472f35f34bbf8d7245cc1db235141aaed7092e47643bbfd5572b0d No new tests failures: FAIL: LLVM :: Bindings/Go/go.test (25308 of 67060) FAIL: ThreadSanitizer-x86_64 :: Darwin/norace-objcxx-run-time.mm (57231 of 67060) FAIL: libunwind :: signal_frame.pass.cpp (64770 of 67060) Thanks, Tobias On Thu, Mar 19, 2020 at 2:51 PM Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:> > Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. > > Source code and docs are available at > https://prereleases.llvm.org/10.0.0/#rc5 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin. > > Thanks, > Hans > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
Neil Nelson via llvm-dev
2020-Mar-20 01:55 UTC
[llvm-dev] [cfe-dev] [10.0.0 Release] Release Candidate 5 is here
Uploaded Xubuntu/Ubuntu 19.10. sha256sum clang+llvm-10.0.0-rc5-x86_64-pc-linux-gnu.tar.xz ac6f43af8278ee0aac17346ff3f15e86b393bcc6b2d6c95fa35dd05f9ff53a38 Only the following fail. FAIL: libFuzzer :: max-number-of-runs.test (60714 of 69913) ******************** TEST 'libFuzzer :: max-number-of-runs.test' FAILED ******************** Script: -- : 'RUN: at line 1'; /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/Phase3/Release+Asserts/llvmCore-10.0.0-rc5.obj/./bin/clang --driver-mode=g++ -O2 -gline-tables-only -fsanitize=address,fuzzer -I/home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/llvm-project/compiler-rt/lib/fuzzer -m64 /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/llvm-project/compiler-rt/test/fuzzer/AccumulateAllocationsTest.cpp -o /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/Phase3/Release+Asserts/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/fuzzer/X86_64DefaultLinuxConfig/Output/max-number-of-runs.test.tmp-AccumulateAllocationsTest : 'RUN: at line 3'; /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/Phase3/Release+Asserts/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/fuzzer/X86_64DefaultLinuxConfig/Output/max-number-of-runs.test.tmp-AccumulateAllocationsTest -seed=1 -runs=2 2>&1 | FileCheck /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/llvm-project/compiler-rt/test/fuzzer/max-number-of-runs.test --check-prefix=CHECK1 : 'RUN: at line 6'; /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/Phase3/Release+Asserts/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/fuzzer/X86_64DefaultLinuxConfig/Output/max-number-of-runs.test.tmp-AccumulateAllocationsTest -seed=1 -runs=3 2>&1 | FileCheck /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/llvm-project/compiler-rt/test/fuzzer/max-number-of-runs.test --check-prefix=CHECK2 : 'RUN: at line 9'; /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/Phase3/Release+Asserts/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/fuzzer/X86_64DefaultLinuxConfig/Output/max-number-of-runs.test.tmp-AccumulateAllocationsTest -seed=1 -runs=4 2>&1 | FileCheck /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/llvm-project/compiler-rt/test/fuzzer/max-number-of-runs.test --check-prefix=CHECK3 -- Exit Code: 1 Command Output (stderr): -- /home/nnelson/Documents/llvm-project/llvm/utils/release/rc5/llvm-project/compiler-rt/test/fuzzer/max-number-of-runs.test:10:9: error: CHECK3: expected string not found in input CHECK3: Done 4 runs ^ <stdin>:1:1: note: scanning from here INFO: Seed: 1 ^ <stdin>:4:56: note: possible intended match here INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes ^ -- ******************** Testing: 0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.. 15 warning(s) in tests Testing Time: 520.48s ******************** Failing Tests (1): libFuzzer :: max-number-of-runs.test Expected Passes : 67697 Expected Failures : 269 Unsupported Tests : 1946 Unexpected Failures: 1 Neil Nelson On 3/19/20 7:51 AM, Hans Wennborg via cfe-dev wrote:> Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. > > Source code and docs are available at > https://prereleases.llvm.org/10.0.0/#rc5 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin. > > Thanks, > Hans > _______________________________________________ > 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/20200319/c96161ba/attachment.html>
Yvan Roux via llvm-dev
2020-Mar-20 07:56 UTC
[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 5 is here
Hi
One new failure for AArch64, binaries uploaded :
a4f0b69af94a4d98389d5a2dfdcb55521591dd7992b5c2a39854cf21512e1daf
clang+llvm-10.0.0-rc5-aarch64-linux-gnu.tar.xz
Failing Tests (2):
AddressSanitizer-aarch64-linux-dynamic :: TestCases/Posix/waitid.cpp
HWAddressSanitizer-aarch64 :: TestCases/global.c
Expected Passes : 65364
Expected Failures : 253
Unsupported Tests : 3382
Unexpected Failures: 2
FAIL: HWAddressSanitizer-aarch64 :: TestCases/global.c (24326 of 69001)
******************** TEST 'HWAddressSanitizer-aarch64 ::
TestCases/global.c' FAILED ********************
Script:
--
: 'RUN: at line 1';
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/./bin/clang
-gline-tables-only -fsanitize=hwaddress -fuse-ld=lld -mllvm
-hwasan-globals -mllvm -hwasan-use-short-granules -mllvm
-hwasan-instrument-landing-pads=0 -mllvm
-hwasan-instrument-personality-functions
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/llvm-project/compiler-rt/test/hwasan/TestCases/global.c
-o
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/hwasan/AARCH64/TestCases/Output/global.c.tmp
: 'RUN: at line 2';
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/hwasan/AARCH64/TestCases/Output/global.c.tmp
0
: 'RUN: at line 3'; not
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/hwasan/AARCH64/TestCases/Output/global.c.tmp
1 2>&1 | FileCheck --check-prefixes=CHECK,RSYM
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/llvm-project/compiler-rt/test/hwasan/TestCases/global.c
: 'RUN: at line 4'; not env
HWASAN_OPTIONS=disable_allocator_tagging=1:random_tags=0:symbolize=0
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/hwasan/AARCH64/TestCases/Output/global.c.tmp
1 2>&1 | FileCheck --check-prefixes=CHECK,RNOSYM
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/llvm-project/compiler-rt/test/hwasan/TestCases/global.c
: 'RUN: at line 5'; not
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/hwasan/AARCH64/TestCases/Output/global.c.tmp
-1 2>&1 | FileCheck --check-prefixes=CHECK,LSYM
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/llvm-project/compiler-rt/test/hwasan/TestCases/global.c
: 'RUN: at line 6'; not env
HWASAN_OPTIONS=disable_allocator_tagging=1:random_tags=0:symbolize=0
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/Phase3/Release/llvmCore-10.0.0-rc5.obj/projects/compiler-rt/test/hwasan/AARCH64/TestCases/Output/global.c.tmp
-1 2>&1 | FileCheck --check-prefixes=CHECK,LNOSYM
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/llvm-project/compiler-rt/test/hwasan/TestCases/global.c
--
Exit Code: 2
Command Output (stderr):
--
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc5/llvm-project/compiler-rt/test/hwasan/TestCases/global.c:16:8:
warning: implicit declaration of function 'atoi' is invalid in C99
[-Wimplicit-function-declaration]
(&x)[atoi(argv[1])] = 1;
On Thu, 19 Mar 2020 at 15:11, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:>
> On Thu, Mar 19, 2020 at 2:51 PM Hans Wennborg <hans at chromium.org>
wrote:
> >
> > Hello again,
> >
> > I had hoped that rc4 would be the last one, but I wanted to pick up
> > one more fix, so here we go.
>
> I should have included this in the previous mail: the fix was for
> https://llvm.org/PR45206
> and I also picked up the fix for https://llvm.org/PR45162 which seemed
low-risk.
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
Bernhard Rosenkraenzer via llvm-dev
2020-Mar-20 13:22 UTC
[llvm-dev] ?==?utf-8?q? [Release-testers] [10.0.0?==?utf-8?q? Release] Release Candidate 5 is here
On Thursday, March 19, 2020 14:51 CET, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:> If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin.Probably not worth making it a blocker, but we've run into this while rebuilding our "unsupported" repo (which is basically a collection of old junk that may still be used by a few people, but that nobody is committing to maintain anymore): https://bugs.llvm.org/show_bug.cgi?id=42925 ttyl bero
Dimitry Andric via llvm-dev
2020-Mar-21 19:11 UTC
[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 5 is here
On 19 Mar 2020, at 14:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:> > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123.For 10.0.0-rc5, I used three patches, which are attached. Main results on amd64-freebsd11: Expected Passes : 67940 (rc4: 67939) Expected Failures : 265 (rc4: 265) Unsupported Tests : 4654 (rc4: 4654) Unexpected Passes : 5 (rc4: 5) Unexpected Failures: 540 (rc4: 540) Individual Timeouts: 18 (rc4: 18) Test suite results on amd64-freebsd11: Expected Passes : 2398 Unexpected Failures: 3 Main results on i386-freebsd11: Expected Passes : 64993 (rc4: 64993) Passes With Retry : 0 (rc4: 1) Expected Failures : 248 (rc4: 248) Unsupported Tests : 3083 (rc4: 3083) Unresolved Tests : 1 (rc4: 1) Unexpected Passes : 5 (rc4: 5) Unexpected Failures: 231 (rc4: 231) Individual Timeouts: 11 (rc4: 9) As usual, the test suite does not build on i386, due to missing SSE and int128 support. The i386 builds are still running, I will upload the tarballs and post the results later. Uploaded: SHA256 (clang+llvm-10.0.0-rc5-amd64-unknown-freebsd11.tar.xz) = 4b27b1bda0f451612475cce6460dad6e82858e88604078913ee736f9f9d834f8 SHA256 (clang+llvm-10.0.0-rc5-i386-unknown-freebsd11.tar.xz) = f6a189006588efe69315cc835b1286403d9b4697ec899ef9935e1bbb10098765 -Dimitry -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-clang-1.diff Type: application/octet-stream Size: 447 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200321/d63a71bb/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-compiler-rt-1.diff Type: application/octet-stream Size: 890 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200321/d63a71bb/attachment-0001.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-test-suite-1.diff Type: application/octet-stream Size: 552 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200321/d63a71bb/attachment-0002.obj> -------------- 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/20200321/d63a71bb/attachment.sig>
Anil Mahmud via llvm-dev
2020-Mar-21 19:12 UTC
[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 5 is here
Hello, I finished testing llvm-10.0.0 RC5 on Power PC 64bit Little Endian Red Hat 7.4 machine and have uploaded the binary from IBM. There were no regressions. The sha1 file is attached. Thanks, Anil Mahmud On Thu, Mar 19, 2020 at 9:51 AM Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote:> Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. > > Source code and docs are available at > https://prereleases.llvm.org/10.0.0/#rc5 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin. > > Thanks, > Hans > _______________________________________________ > 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/20200321/5c59b283/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-10.0.0-rc5-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/20200321/5c59b283/attachment.obj>
Michał Górny via llvm-dev
2020-Mar-21 20:00 UTC
[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 5 is here
On Thu, 2020-03-19 at 14:51 +0100, Hans Wennborg via Release-testers wrote:> Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. >I realize it's late but I've just gotten a major bug report. Long story short, if you happen to have CUDA toolkit 10.2 installed, clang throws warnings on every compilation (even non-CUDA) which in turns breaks CMake checks, which in turn means you can't compile pretty much anything correctly (including LLVM itself). I've filed a backport request: https://bugs.llvm.org/show_bug.cgi?id=45270 -- Best regards, Michał Górny -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 618 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200321/054196a4/attachment.sig>
Andrew Kelley via llvm-dev
2020-Mar-22 20:05 UTC
[llvm-dev] [10.0.0 Release] Release Candidate 5 is here
On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote:> Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. > > Source code and docs are available at > https://prereleases.llvm.org/10.0.0/#rc5 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin.I went ahead and updated all Zig's CI to use rc5, and ran into this problem: /usr/lib/llvm-10/lib/libclangCodeGen.a(BackendUtil.cpp.o): In function `(anonymous namespace)::EmitAssemblyHelper::EmitAssemblyWithNewPassManager(clang::BackendAction, std::unique_ptr<llvm::raw_pwrite_stream, std::default_delete<llvm::raw_pwrite_stream> >)': BackendUtil.cpp:(.text._ZN12_GLOBAL__N_118EmitAssemblyHelper30EmitAssemblyWithNewPassManagerEN5clang13BackendActionESt10unique_ptrIN4llvm17raw_pwrite_streamESt14default_deleteIS5_EE+0x16df): undefined reference to `getPollyPluginInfo()' collect2: error: ld returned 1 exit status This is on Ubuntu Bionic, using apt.llvm.org. I believe this is https://bugs.llvm.org/show_bug.cgi?id=44870 / https://github.com/llvm/llvm-project/issues/191 This is a regression from LLVM 9. My suggestion to fix this is, rather than cutting rc6, to update apt.llvm.org with new binaries, which have polly disabled. It seems to me that people who want Polly enabled are compiling from source anyway. Regards, Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200322/3fe147dd/attachment.sig>
James Henderson via llvm-dev
2020-Mar-23 08:55 UTC
[llvm-dev] [cfe-dev] [10.0.0 Release] Release Candidate 5 is here
Hi Hans, I don't know if you'll be planning on RC6, but this bug: https://bugs.llvm.org/show_bug.cgi?id=45271 was just filed as a regression in LLVM 10 versus LLVM 9, and looks like it could break things (potentially silently) for at least some installations of llvm-strip. There's a fix that's basically ready (https://reviews.llvm.org/D76562). I'll leave it up to you as to whether the fix should be included in the release or not (it almost certainly should be in a patch release if it doesn't, I think). James On Thu, 19 Mar 2020 at 13:51, Hans Wennborg via cfe-dev < cfe-dev at lists.llvm.org> wrote:> Hello again, > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. > > Source code and docs are available at > https://prereleases.llvm.org/10.0.0/#rc5 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > you still have cycles, please take this for a quick spin. > > Thanks, > Hans > _______________________________________________ > cfe-dev mailing list > cfe-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200323/97885d4d/attachment.html>
Hans Wennborg via llvm-dev
2020-Mar-23 14:49 UTC
[llvm-dev] [10.0.0 Release] Release Candidate 5 is here
On Sun, Mar 22, 2020 at 9:05 PM Andrew Kelley <andrew at ziglang.org> wrote:> > On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote: > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > > release branch at 35627038123. > > > > Source code and docs are available at > > https://prereleases.llvm.org/10.0.0/#rc5 and > > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > > > If nothing new comes up, I plan to tag 'final' on Monday. Testers, if > > you still have cycles, please take this for a quick spin. > > I went ahead and updated all Zig's CI to use rc5, and ran into this problem: > > /usr/lib/llvm-10/lib/libclangCodeGen.a(BackendUtil.cpp.o): In function > `(anonymous > namespace)::EmitAssemblyHelper::EmitAssemblyWithNewPassManager(clang::BackendAction, > std::unique_ptr<llvm::raw_pwrite_stream, > std::default_delete<llvm::raw_pwrite_stream> >)': > BackendUtil.cpp:(.text._ZN12_GLOBAL__N_118EmitAssemblyHelper30EmitAssemblyWithNewPassManagerEN5clang13BackendActionESt10unique_ptrIN4llvm17raw_pwrite_streamESt14default_deleteIS5_EE+0x16df): > undefined reference to `getPollyPluginInfo()' > collect2: error: ld returned 1 exit status > > > This is on Ubuntu Bionic, using apt.llvm.org. I believe this is > https://bugs.llvm.org/show_bug.cgi?id=44870 / > https://github.com/llvm/llvm-project/issues/191 > > This is a regression from LLVM 9. My suggestion to fix this is, rather > than cutting rc6, to update apt.llvm.org with new binaries, which have > polly disabled. It seems to me that people who want Polly enabled are > compiling from source anyway.That sounds reasonable to me. +Sylvestre Ledru do you control these package configs?
Hans Wennborg via llvm-dev
2020-Mar-23 14:50 UTC
[llvm-dev] [cfe-dev] [10.0.0 Release] Release Candidate 5 is here
I think it's too late for this, but distributions that install the tool like that may want to take that patch downstream. On Mon, Mar 23, 2020 at 9:55 AM James Henderson <jh7370.2008 at my.bristol.ac.uk> wrote:> > Hi Hans, > > I don't know if you'll be planning on RC6, but this bug: https://bugs.llvm.org/show_bug.cgi?id=45271 was just filed as a regression in LLVM 10 versus LLVM 9, and looks like it could break things (potentially silently) for at least some installations of llvm-strip. There's a fix that's basically ready (https://reviews.llvm.org/D76562). I'll leave it up to you as to whether the fix should be included in the release or not (it almost certainly should be in a patch release if it doesn't, I think). > > James > > On Thu, 19 Mar 2020 at 13:51, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> >> Hello again, >> >> I had hoped that rc4 would be the last one, but I wanted to pick up >> one more fix, so here we go. >> >> Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the >> release branch at 35627038123. >> >> Source code and docs are available at >> https://prereleases.llvm.org/10.0.0/#rc5 and >> https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 >> >> If nothing new comes up, I plan to tag 'final' on Monday. Testers, if >> you still have cycles, please take this for a quick spin. >> >> Thanks, >> Hans >> _______________________________________________ >> cfe-dev mailing list >> cfe-dev at lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev