14.0.5-final has been tagged

Project Infrastructure Release Testers
1

Hi,

14.0.5-final has been tagged, please upload your binaries and test results.

-Tom

2

macOS builds are up: 66cf1b8e00289a567b2f5f740f068b7682e27ccf048647b836d3624376a64705

test failures:

FAIL: Clang :: Driver/darwin-ld-lto.c (8207 of 96953)
FAIL: Flang :: Runtime/no-cpp-dep.c (33374 of 96953)
FAIL: LLVM :: ExecutionEngine/JITLink/X86/MachO_x86-64_self_relocation_exec.test (56542 of 96953)
FAIL: ORC-x86_64-darwin :: TestCases/Darwin/x86-64/trivial-cxa-atexit.S (82501 of 96953)
FAIL: ORC-x86_64-darwin :: TestCases/Darwin/x86-64/trivial-static-initializer.S (82502 of 96953)
FAIL: ORC-x86_64-darwin :: TestCases/Darwin/x86-64/trivial-tlv.S (82503 of 96953)
FAIL: ORC-x86_64-darwin :: TestCases/Darwin/x86-64/trivial-objc-methods.S (82504 of 96953)
FAIL: ORC-x86_64-darwin :: TestCases/Darwin/x86-64/trivial-swift-types-section.S (82515 of 96953)
FAIL: flang-OldUnit :: Evaluate/folding.test (85838 of 96953)
FAIL: libomp :: ompt/loadtool/tool_available_search/tool_available_search.c (94098 of 96953)
FAIL: libomp :: tasking/hidden_helper_task/gtid.cpp (94198 of 96953)
FAIL: libomp :: worksharing/for/kmp_sch_simd_guided.c (94246 of 96953)

No regressions from 14.0.4.

3

For 14.0.5 final, I have built and tested on both FreeBSD 12 and 13. No additional patches were needed.

Main results on amd64-freebsd12:

  Skipped            :     4 (14.0.4:     4)
  Unsupported        :  6771 (14.0.4:  6768)
  Passed             : 97036 (14.0.4: 97032)
  Expectedly Failed  :   314 (14.0.4:   314)
  Timed Out          :     4 (14.0.4:     5)
  Failed             :   170 (14.0.4:   170)
  Unexpectedly Passed:     2 (14.0.4:     2)

Test suite results on amd64-freebsd12:

  Passed: 2420 (14.0.4: 2420)
  Failed:    3 (14.0.4:    3)

Main results on amd64-freebsd13:

  Skipped            :     4 (14.0.4:     4)
  Unsupported        :  6771 (14.0.4:  6768)
  Passed             : 96996 (14.0.4: 96994)
  Expectedly Failed  :   314 (14.0.4:   314)
  Timed Out          :     6 (14.0.4:     4)
  Failed             :   208 (14.0.4:   209)
  Unexpectedly Passed:     2 (14.0.4:     2)

Test suite results on amd64-freebsd13:

  Passed: 2420 (14.0.4: 2420)
  Failed:    3 (14.0.4:    3)

Uploaded:

SHA256 (clang+llvm-14.0.5-amd64-unknown-freebsd12.tar.xz) = 1edee096aa23e2c0b75352953c4f04a105fd9521de6742d4652b44ab9009636c
SHA256 (clang+llvm-14.0.5-amd64-unknown-freebsd13.tar.xz) = 52c62e29f2cd8d72d592cded337e47bb8cb0998f7ee5f3c1b168790bdce154e7

-Dimitry

4

Windows is ready. sha256sums:

21cbd9485006ebecfb081c467b884a25bcb282a723e595742c423d1925b857e0 LLVM-14.0.5-win32.exe
7b3f8f9255eb36422fadefc2828e33b55f7cda0270860defe196cb24fd06abfe LLVM-14.0.5-win64.exe

Built with llvm\utils\release\build_llvm_release 14.0.5 at llvm revision 7e5f75aa37801b9e4e9f0e3fb9f0358cbafb6f63.

5

Arm ready:

e8138f24d716ef9714e259ab276e6ef74c8adcf9af0270464a8a01c24a583ea8  clang+llvm-14.0.5-aarch64-linux-gnu.tar.xz
f80dbd2684f8fe13ce675236e5ef0235fdf5239d442c21f066245d7fb98ba11c  clang+llvm-14.0.5-armv7a-linux-gnueabihf.tar.xz
531d5dae6e5cffab5587379df6c56e7fa32226f8a01c1a84a9395c9deb93d290  LLVM-14.0.5-woa64.zip

No changes in the test results.

6

The PowerPC (AIX 7.2) binaries for 14.0.5 have been uploaded.
Once again, compiler-rt was built as a runtime (and not as a project). No regressions were found.

87572ebec77dfe8c016e30f3d11a667989f89fed  clang+llvm-14.0.5-powerpc64-ibm-aix-7.2.tar.xz
7

Hi! The PowerPC (Linux) binaries for LLVM 14.0.5 binaries have been uploaded.

For Ubuntu 18.04.5:

b0eb87cabf9f57453c85f0e23e4ca56b5d8be4a3  clang+llvm-14.0.5-powerpc64le-linux-ubuntu-18.04.5.tar.xz

For RHEL 8.4:

5c3ab1bb217904566520770fda12b817df395d7b  clang+llvm-14.0.5-powerpc64le-linux-rhel-8.4.tar.xz

The testing overall went well - although I did find an issue that occurs when testing with -Werror regarding an AVR patch. I’ve left a comment about it in https://github.com/llvm/llvm-project/issues/45485#issuecomment-1157160112. I believe this issue shown up for @jakeegan for AIX, as well.

8

@amy-kwan I’m planning to do a 14.0.6 release to fix this issue.