[11.0.0 Release] Release Candidate 5 is here

Hello again,

We had to pick up another bug fix, so here is another release
candidate: llvmorg-11.0.0-rc5 tag was just created.

Source code and docs are available at
https://prereleases.llvm.org/11.0.0/#rc5
and
https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5

Pre-built binaries will be added as they become ready.

Please file reports for any bugs you find as blockers of
https://llvm.org/pr46725

Release testers, if you still have cycles (perhaps you didn't even
have time to start rc4 yet), please run the test script, share your
results, and upload binaries.

As mentioned above, this rc is very similar to the previous one. There
are no open blockers, so it could be the last release candidate.

Thanks,
Hans

Just a heads up - I won’t be able to do any macOS builds for a bit - my mac pro has died and needs to be replaced. I hope to get a replacement next week, but meanwhile I won’t be able to do any testing or binary uploads.

Let me know if anyone else with a mac have some CPU cycles to spare for this release.

I’m happy to run them, although I’d appreciate a pointer to the appropriate documentation.

Shoabi,

Thanks that would be great - llvm comes with a script that builds and runs the tests in llvm/utils/release/test-release.sh

I usually create a release directory and then invoke it like this
…/llvm/utils/release/test-release.sh -release 11.0.0 -rc 5 -triple x86_64-apple-darwin -use-ninja -j

That takes two hours or so then I inspect the log file for testing errors:

grep “FAIL:” logs/testing-rc5.txt (I think don’t remember exactly the name of the file).

make sha256 sum: shasum -a 256 clang+llvm-…tar.xz

And then upload to the sftp server, but in this case - feel free to put it on gdrive or something like that and I can upload it to the sftp server for Hans to add to the release.

Thanks for helping out!

– Tobias

Thanks! I’m running that now and will report back when it’s done.

Uploaded Ubuntu 20.04.

sha256sum clang+llvm-11.0.0-rc5-x86_64-linux-gnu-ubuntu-20.04.tar.xz
c7d6cd6c9b96af7ba4315339e0663e5d5218aafcafbe086a7b148cf76aa6a70c

Testing Time: 347.68s
Unsupported : 1759
Passed : 69942
Expectedly Failed: 248
[100%] Built target check-all

llvm-test-suite
Testing Time: 1046.69s
Passed: 2405

Neil Nelson

https://www.dropbox.com/s/ovb47c2rpmr2c17/clang%2Bllvm-11.0.0-rc5-x86_64-apple-darwin.tar.xz?dl=1

2d4163b1fb5c5d1514883f7ce02286dc63befad70b02ad9c368a0b861bf5dfb5 clang+llvm-11.0.0-rc5-x86_64-apple-darwin.tar.xz

Two libunwind tests failed for me. I haven’t dug into why; has this been seen before?

libunwind :: libunwind_01.pass.cpp

libunwind :: signal_frame.pass.cpp

What I usually do is

grep -n ‘Expectedly Failed’ testing.11.0.0-rc5.log

This will give two lines (shown here as examples).

99700: Expectedly Failed: 241
211999: Expectedly Failed: 248

Get the text around the second line.

sed -n 211980,212005p testing.11.0.0-rc5.log

It sounds like you are saying there are two errors and that may appear in the totals counts in an Unexpected Failures line after the Expectedly Failed line.

The detail of the errors will commonly be immediately above the totals counts area and can be seen by reducing the start line number enough in the above sed command. You can then copy the errors to the llvm-dev list or create a blocking bug tied to as noted below.

Neil Nelson

I've built both rc4 and rc5, and again these did not need any patches.

Main results on amd64-freebsd11:

  Unsupported : 5122 (rc4: 5122, rc3: 5122)
  Passed : 69761 (rc4: 69761, rc3: 69761)
  Expectedly Failed : 245 (rc4: 245, rc3: 245)
  Timed Out : 16 (rc4: 16, rc3: 16)
  Failed : 481 (rc4: 481, rc3: 480)
  Unexpectedly Passed: 2 (rc4: 2, rc3: 2)

Test suite results on amd64-freebsd11:

  Passed: 2399 (rc4: 2399, rc3: 2399)
  Failed: 3 (rc4: 3, rc3: 3)

Main results on i386-freebsd11:

  Unsupported : 3513 (rc4: 3513, rc3: 3513)
  Passed : 66637 (rc4: 66637, rc3: 66636)
  Expectedly Failed : 230 (rc4: 230, rc3: 230)
  Timed Out : 7 (rc4: 7, rc3: 7)
  Failed : 321 (rc4: 321, rc3: 321)
  Unexpectedly Passed: 1 (rc4: 1, rc3: 1)

Uploaded:
SHA256 (clang+llvm-11.0.0-rc4-amd64-unknown-freebsd11.tar.xz) = b95c237df671ee507c607e8d36245126c5ea5241389aae0b20e3e4fce4f3df37
SHA256 (clang+llvm-11.0.0-rc4-i386-unknown-freebsd11.tar.xz) = 60755863b49155d23c9fef9571aa09ca46425a9bd830d9ef498fe9855e741d11
SHA256 (clang+llvm-11.0.0-rc5-amd64-unknown-freebsd11.tar.xz) = 712401cade6996bb7042cdd659b41ee4411cdd9cc34cbdd21e7a4cafe75ac267
SHA256 (clang+llvm-11.0.0-rc5-i386-unknown-freebsd11.tar.xz) = 956bd26d28602f375853593631c1f413a869ba6087c51f7ef5405fa31263d06c

-Dimitry

Sorry, my Dropbox account got restricted yesterday. The link should work again right now, and I also uploaded it to clang+llvm-11.0.0-rc5-x86_64-apple-darwin.tar.xz - Google Drive

Full test results were

Testing Time: 3081.58s
  Unsupported : 3200
  Passed : 68252
  Expectedly Failed: 264
  Failed : 2

I looked into the libunwind failures. There was a misconfiguration resulting in the compiled libunwind not actually being linked against the tests (they were linking against the system unwinder instead), and fixing that fixed libunwind_01.pass.cpp. signal_frame.pass.cpp is failing because the unwinder doesn't recognize signal frames; I don't know if that's expected with the compact unwind encoding format that's used for Mach-O, and I'm CCing Saleem in case he knows. libunwind doesn't appear to have a Bugzilla category, so I'm not sure how best to proceed here and if this test failure should be considered launch-blocking. The test also fails for me with 10.0.1, so it's not a regression in that sense.

    Hey Shoaib,

    The dropbox link is 404 for me.

    -- Tobias

Hi Hans,

Release testing for llvm-11.0.0-rc5 on Power PC 64bit Little Endian for Ubuntu 18.04 and Red Hat 7.4 is completed, did not see any regressions.
I have uploaded the respective binaries and have attached the sha1 files.

Thank you,
Amy K.

clang+llvm-11.0.0-rc5-powerpc64le-linux-rhel-7.4.sha1 (98 Bytes)

clang+llvm-11.0.0-rc5-powerpc64le-linux-ubuntu-16.04.sha1 (106 Bytes)

Uploaded binaries for SLES12 and Ubuntu 16 x86_64. I realized that I’d forgotten rc3,4 ones so I uploaded them too.

$ cat clang+llvm-11.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
clang+llvm-11.0.0-rc3-x86_64-linux-sles12.4.tar.xz.sha256
clang+llvm-11.0.0-rc4-x86_64-linux-sles12.4.tar.xz.sha256
clang+llvm-11.0.0-rc5-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
clang+llvm-11.0.0-rc5-x86_64-linux-sles12.4.tar.xz.sha256

aaf668664769dfb071c59f5d2622f3459d457b58489ee79f69262cef8cf2abb4 clang+llvm-11.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
93394ee58b18ec72bf4455dc6055a9ba5100621282547c686bd4ef689fe1d8a5 clang+llvm-11.0.0-rc3-x86_64-linux-sles12.4.tar.xz
91a0984c7d0be93af310a1d762e34e283952ce9734ecec040b6a90fd31466150 clang+llvm-11.0.0-rc4-x86_64-linux-sles12.4.tar.xz
af8daead4a6d996fab7630759a9330d5eb0ceea06dbd6daa7fdd92126b0f02ee clang+llvm-11.0.0-rc5-x86_64-linux-gnu-ubuntu-16.04.tar.xz
b57ef3689a6bf161dab3fee644fe0837e1c9cb31875556f7be259b8eaf64a43d clang+llvm-11.0.0-rc5-x86_64-linux-sles12.4.tar.xz

Hans,

I have uploaded clang+llvm-11.0.0-rc5-x86_64-apple-darwin.tar.xz to
the sftp for you.

Shoaib - thanks for doing this build and checking out the test
failures. I didn't see any failures on my machine before as far as I
can remember - unfortunately I can't double check now with my machine
fried. I wonder if it's a difference in setup or me just missing it?
Anyway since it's not a regression compared to 10.0.1 - I don't see it
as a blocker for the 11 release.

Thanks,
Tobias

Hi,

Uploaded arm & aarch64:
935653ab6618ed557bbb6d5e5af9ad97efa4bfa526a29ed8701dc3698084769b
clang+llvm-11.0.0-rc5-armv7a-linux-gnueabihf.tar.xz
1b824b5188de0bd99444825572c0e1491e2e1eae85e484450724cffd4cf5f316
clang+llvm-11.0.0-rc5-aarch64-linux-gnu.tar.xz

No new issues.

Cheers,
Diana

Windows is ready:

$ sha256sum LLVM-11.0.0-rc5-win*.exe
73e0e3bfe35706b0ca864c78d111a6ceead01e1d27affdf42571bb5061fdab40
LLVM-11.0.0-rc5-win32.exe
eb92a405cab8f570416528235aff97b0a4fa30109bae2a5e79bb540526da9c55
LLVM-11.0.0-rc5-win64.exe