18.1.0 final tagged

tstellar · March 6, 2024, 6:01am

I’ve tagged the 18.1.0 final release. Please test, upload binaries, and report issues to the issue tracker.

hansw2000 · March 6, 2024, 10:26am

Windows is ready. Hashes:

C:\src>certutil -hashfile llvm_package_18.1.0\build32\LLVM-18.1.0-win32.exe sha256
SHA256 hash of llvm_package_18.1.0\build32\LLVM-18.1.0-win32.exe:
1f1e65b6d6555d77db40183c9ae934b622618875337e1181d952cf2f808bfcfd
CertUtil: -hashfile command completed successfully.

C:\src>certutil -hashfile llvm_package_18.1.0\build64\LLVM-18.1.0-win64.exe sha256
SHA256 hash of llvm_package_18.1.0\build64\LLVM-18.1.0-win64.exe:
6cfba817605e509f363c6b010f766e172e1cbdd05de4d77bfee12cf185e59095
CertUtil: -hashfile command completed successfully.

C:\src>certutil -hashfile "llvm_package_18.1.0\clang+llvm-18.1.0-x86_64-pc-windows-msvc.tar.xz" sha256
SHA256 hash of llvm_package_18.1.0\clang+llvm-18.1.0-x86_64-pc-windows-msvc.tar.xz:
d128c0f5f7831c77d549296a910fc9972407ff028b720fb628ffa837ed7ff04e
CertUtil: -hashfile command completed successfully.

They were built with llvm-project\llvm\utils\release\build_llvm_release.bat --x86 --x64 --version=18.1.0 using the script at 52ada07.

rorth · March 6, 2024, 1:52pm

I’ve just uploaded release tarballs for Solaris 11.4/amd64, Solaris 11.4/sparcv9, and Linux/sparc64:

c352b81dd6add029e3def54a7b90387bb1df15f76497adac0b9f305694eb2d8c  clang+llvm-18.1.0-amd64-pc-solaris2.11.tar.xz
e871f472ceafbe0197cff81d7240552e45e55ead00fe82f4fb326af32bbfb657  clang+llvm-18.1.0-sparcv9-sun-solaris2.11.tar.xz
0f6d94d9e3eccb5596def41e48b3f8a400f27edc2374e6fc53d0b6baea0d79b3  clang+llvm-18.1.0-sparcv9-unknown-linux-gnu.tar.xz

No regressions from rc4.

brooks · March 6, 2024, 9:03pm

FYI: LLVM_VERSION_SUFFIX is still being set to rc in llvm/CMakeLists.txt

NancyWang2019 · March 6, 2024, 9:50pm

can someone help fix this line llvm-project/llvm/CMakeLists.txt at release/18.x · llvm/llvm-project · GitHub

brooks · March 6, 2024, 10:17pm

FWIW, I’m working around this in the FreeBSD ports collection by building with -DLLVM_VERSION_SUFFIX=

I’ll probably keep this around for future RC builds as we don’t find the suffix useful in practice.

tstellar · March 6, 2024, 11:42pm

Is this causing any issues for you?

NancyWang2019 · March 7, 2024, 12:01am

we just want to show correct clang version with clang -version option, it outputs 18.1.0rc , if looked at 17.x branch, there is commit to set it empty after created tag 17.0.0 , see this commit Initiating SAML single sign-on, if not fix any time soon we may also work around this by using -DLLVM_VERSION_SUFFIX= , will let you know. Thanks

amy-kwan · March 7, 2024, 4:38am

Hi!

The testing for PowerPC (Linux) is complete and I’ve uploaded the binary:

ea8b9ef8827ec59370eb77822461e1986376750c  clang+llvm-18.1.0-powerpc64le-linux-rhel-8.8.tar.xz

No regressions were found.

DimitryAndric · March 7, 2024, 6:04pm

FWIW, during the earlier release phase I ran into an issue with the FreeBSD devel/build2 port, which was reported upstream here:

github.com/build2/build2

clang 'rc' or 'git' version numbers are not parsed correctly

opened 08:25PM - 01 Feb 24 UTC

closed 06:00PM - 02 Feb 24 UTC

DimitryAndric

While doing some preparation work for merging clang 18 into FreeBSD, I ran into …a failure building the devel/build2 port. What appears to happen is that build2 cannot handle the version declared by the clang binary in the base system, which is (at this point): ```text FreeBSD clang version 18.1.0rc (https://github.com/llvm/llvm-project.git llvmorg-18-init-18361-g22683463740e) ``` It appears `build2::cc::guess_clang` skips over all words except the last one (`llvmorg-18-init-18361-g22683463740e)`) and then fails to parse that string as a version. It then dies with: ```text error: unable to extract Clang minor version from '18' info: use config.cxx.version to override ``` What I find a little strange is that `guess_clang` does not seem to look for the "version" word at all. Normally, the version directly follows that word. But apparently it goes over all words in the version string, and considers the first one that contains only digits and a dot as a candidate. However, git versions of clang are typically marked `18.0.0git`, while release candidates such as the current rc1 are marked `18.1.0rc`. Maybe it is a bit overkill to also support these syntaxes, because when the final release is done the suffix is removed, and it will become a regular 3 piece decimal number with dots again. In any case I would like your opinion on whether it is better to pass explicit `config.cxx.version` in such cases, or whether the version parser in `guess_clang` can be improved?

But that was caused by build2 having certain assumptions about the formatting of the version string, which fell over due to the new “rc” suffix.

alison.zhang · March 11, 2024, 1:30pm

The AIX 7.2 binaries have been uploaded:
ba3588721654bbbe5e8bfc6a4e827520b891ee9e clang+llvm-18.1.0-powerpc64-ibm-aix-7.2.tar.xz

No regressions were found.

omjavaid · March 12, 2024, 8:53am

I have uploaded following binaries for 18.1.0

LLVM-18.1.0-woa64.exe
f92f14beae87dd40bfb06845c72d7211830db1334035d07fff25bd39b7fe03c4

clang+llvm-18.1.0-aarch64-linux-gnu.tar.xz
32faaad5b6e072d763a603f7c51e4ee63e2d82c16e945524a539df84e3f2b058

clang+llvm-18.1.0-armv7a-linux-gnueabihf.tar.gz
bfbd3bb71f4a1aaf8f1e13cf681e16a54f1029e7f5c85492812bf93a1d893dc8

No new test failures since 18.1.0 rc4.

Topic		Replies	Views
18.1.3 has been tagged Release Testers	4	194	April 8, 2024
18.1.4 has been tagged Release Testers	6	235	April 28, 2024
18.1.1 Tagged Release Testers	5	241	March 17, 2024
LLVM 18.1.0-rc1 tagged Release Testers	16	466	March 26, 2024
LLVM 18.1.0-rc4 tagged Release Testers	9	235	March 7, 2024

18.1.0 final tagged

Related Topics