14.0.0-rc2 has been tagged

Hi,

I’ve tagged 14.0.0-rc2. Please upload the binaries to GitHub and report any bugs you find.

-Tom

Windows is ready. Here are the sha256sums:

c3fef804adcebfdf6158bd9da9399a5f2698b3f2b603bfc69f6c7865a48e8ebc LLVM-14.0.0-rc2-win32.exe
6e522f69d57c3ccf935e6595e0f05bef245c9d4fbd8b04570b67aba73bf5006f LLVM-14.0.0-rc2-win64.exe

Since OpenMP runtime fails to build on Windows: openmp\runtime\src\kmp_affinity.cpp(951): error C2131: expression did not evaluate to a constant · Issue #53672 · llvm/llvm-project · GitHub got fixed, the OpenMP runtime is now part of the packages again.

Also, as discussed in Python 3.6 End of Life · Issue #53738 · llvm/llvm-project · GitHub LLDB is now built against a more recent version of Python (3.10).

The packages were built with the attached batch file: build_llvm_1400-rc2.bat.txt (5.2 KB)

1 Like

With this rc2 I am seeing the same phenomenon as with the previous rc1, which is that way less regression tests are being run. For instance, with 13.0.1:

# Testing - built with clang
[1/1338] Running lint check for sanitizer sources...
...
[1337/1338] Running all regression tests
...
-- Testing: 98828 tests, 2 workers --

but with 14.0.0 rc1 only ~15000 tests are run:

# Testing - built with clang
[1/1227] Building CXX object tools/clang/tools/extra/unittests/clang-apply-replacements/CMakeFiles/ClangApplyReplacementsTests.dir/ApplyReplacementsTest.cpp.o
...
[219/220] Running all regression tests
...
-- Testing: 15038 tests, 2 workers --

I also have an idea what the culprit is: the new LLVM_ENABLE_RUNTIMES CMake option, and the associated new check-runtimes target: in the CMake files, the traditional check-all target now has check-runtimes as a dependency… This means that if there is any error in check-runtimes, the rest of check-all is completely skipped!

Am I correct in thinking that this is the cause for ~85000 missing tests?

Do we need some kludge to make check-all continue, regardless of the success or failure of check-runtimes ?

Can you file an issue for this?

I’ve now uploaded the Solaris binaries. sha256sums are

03ec89dd71fbf0e9bb68613641604fa5881979aad3c86b5c16813a92e6b84c95  clang+llvm-14.0.0-rc2-sparcv9-sun-solaris2.11.tar.xz
7e3c858f847a2f86ccececcc17e3de81048b5a60f782c67cba22a73bd4b31205  clang+llvm-14.0.0-rc2-x86_64-pc-solaris2.11.tar.xz

Fixes for all the build failures in rc1 have been integrated. Thanks!

There’s one issue that I almost missed due to Issue #54154 above, but got prominent when manually re-running the tests with

ninja -k0 check-llvm check-clang check-clang-tools check-compiler-rt check-polly check-mlir check-flang

(Hope I didn’t miss any above.)

Quite a number of tests now failed due to the change in runtime lib directory layout due to the use of -DLLVM_ENABLE_RUNTIMES=. I’ve filed Issue #54196 for this. The uploaded binaries work around it by configuring for x86_64-pc-solaris2.11 instead of the canonical amd64-pc-solaris2.11.

1 Like

Linux PowerPC binaries are clean. I’ve uploaded the binaries:

60159f4e5c88a4086f43746ee85c0e61e427b45e  clang+llvm-14.0.0-rc2-powerpc64le-linux-rhel-7.9.tar.xz
834fffccc8f439278e57f26aa87fb2af6c5b236d  clang+llvm-14.0.0-rc2-powerpc64le-linux-ubuntu-18.04.5.tar.xz
1 Like

Uploaded armv7-linux, aarch64-linux and WoA:

04123a24288fadee8d6e9b640f4e0739d003aca1e645d1d5d6141652bc8c152d  clang+llvm-14.0.0-rc2-aarch64-linux-gnu.tar.xz
b226c34dd323a384b21ba0eea31967b620e8755d2c87fae30122e26a154a3b33  clang+llvm-14.0.0-rc2-armv7a-linux-gnueabihf.tar.xz
1cde7a16334216b5f6ee0049f4a4706dee811ae9806cb7e38b754b2a99cdb780  LLVM-14.0.0-rc2-woa64.zip

Looks mostly the same as rc1, except for the fact that I’m no longer seeing differences between Phase2 and Phase3 object files on aarch64. Curiously enough, they’re still there on armv7.

1 Like

Hi,

I’ve uploaded the PowerPC (AIX 7.2) binaries for rc2.

d094a044cd969c2a066ce40f4776c4ce717d0d72  clang+llvm-14.0.0-rc2-powerpc64-ibm-aix-7.2.tar.xz

No new regressions were seen when testing RC2 on AIX.

1 Like

Uploaded x86_64 Ubuntu 18.04 binaries for rc2.

$ cat clang+llvm-14.0.0-rc2-x86_64-linux-gnu-ubuntu-18.04.tar.xz.sha256
4e6e570f07695bc8ea7e7b5c049e1a9fcf53d4d44f4bfc232386ee1c90c95eab  clang+llvm-14.0.0-rc2-x86_64-linux-gnu-ubuntu-18.04.tar.xz
1 Like

Nothing special.
I just had something unusual in Ubuntu Jammy (the next one)
lldb Python files are installed in
usr/lib/llvm-14/local/lib/python3*/*-packages/lldb/
instead of
usr/lib/llvm-14/lib/python3*/*-packages/lldb/

(i just moved back the files as workaround)

Seems to be a change in Ubuntu, not a LLVM issue but documenting for others.