I’ve tagged the 18.1.0-rc4 release. Please test, upload binaries, and report issues to the issue tracker. If there are no major issues, then this will become the final release.
I’ve now uploaded Solaris/amd64, Solaris/sparcv9, and Linux/sparc64 tarballs:
808fe6aad6f470fb5f0da6ae1992c6d9e0fa312629b0e379ffeba0b23ab1650b clang+llvm-18.1.0-rc4-amd64-pc-solaris2.11.tar.xz
5386363b3dd2b23f5818373bbdcea5340a23beaf41e25c4b563b8450a855ff3e clang+llvm-18.1.0-rc4-sparcv9-sun-solaris2.11.tar.xz
1817218e6d509e5b541316513b8232e4f40b30835bcc88a8f9e304d5c462a2d7 clang+llvm-18.1.0-rc4-sparcv9-unknown-linux-gnu.tar.xz
No regressions from rc3.
Windows is ready.
Hashes:
C:\src>certutil -hashfile llvm_package_18.1.0-rc4\build32\LLVM-18.1.0-rc4-win32.exe sha256
SHA256 hash of llvm_package_18.1.0-rc4\build32\LLVM-18.1.0-rc4-win32.exe:
a769d648642eef1fd8eccc8d36c499d2131a39f4e4807c3aa1d5e529d42c6a6a
CertUtil: -hashfile command completed successfully.
C:\src>certutil -hashfile llvm_package_18.1.0-rc4\build64\LLVM-18.1.0-rc4-win64.exe sha256
SHA256 hash of llvm_package_18.1.0-rc4\build64\LLVM-18.1.0-rc4-win64.exe:
c3ee60063428abada2d405dc6838ca06b09d8fa5ad18414bde4f46b361c7820b
CertUtil: -hashfile command completed successfully.
C:\src>certutil -hashfile "llvm_package_18.1.0-rc4\clang+llvm-18.1.0-rc4-x86_64-pc-windows-msvc.tar.xz" sha256
SHA256 hash of llvm_package_18.1.0-rc4\clang+llvm-18.1.0-rc4-x86_64-pc-windows-msvc.tar.xz:
3d43aa144961368b4a8783279e4e94e2483063938911acf2c9c35a995f486a73
CertUtil: -hashfile command completed successfully.
They were built with llvm-project\llvm\utils\release\build_llvm_release.bat --x86 --x64 --version=18.1.0-rc4 using the script at 52ada07
Hi @tstellar, would it be possible to cherry-pick commit 3af5c98 into the release? Otherwise, the test-release.sh script fails at the beginning of Phase 2 on AIX.
Sorry, I missed this one, but you can run the test-release.sh script from the main branch, so this shouldn’t be a blocker.
Thank you
I have uploaded following releases:
➜ rc4 sha256sum clang+llvm-18.1.0-rc4-armv7a-linux-gnueabihf.tar.gz
76c8248a2e9da72c94817eb68a829c5e1c55b739648067aedfada58daac616c7
➜ rc4 sha256sum clang+llvm-18.1.0-rc4-aarch64-linux-gnu.tar.xz
a11483d702754bcc432b3d8ad837c5b762928bccf1b9e2883f81083f70e69838
➜ rc4 sha256sum LLVM-18.1.0-rc4-woa64.exe
d22709602bb6c429dc041b2051560f89dfd3a52d529909c80308b81620f5fdd0
No change in test result situation since 18.0.1 rc3.
Linux PowerPC testing completed and binary uploaded, no regression found.
65212062a789f673baa52d810e425d4bef4734f9 clang+llvm-18.1.0-rc4-powerpc64le-linux-rhel-8.8.tar.xz
The AIX 7.2 binaries have been uploaded:
95a0943a4dceaf044fbab9eae4d55b16f892a548 clang+llvm-18.1.0-rc4-powerpc64-ibm-aix-7.2.tar.xz
Appending -configure-flags "-DCMAKE_C_FLAGS=\"-pthread\" -DCMAKE_CXX_FLAGS=\"-pthread\"" to the test-release.sh configuration fixed the failures in this issue. There are no regressions otherwise.