Hi,
I have just tagged the 10.0.1-rc1 release. Testers can begin testing and uploading
binaries.
If you still want to get a fix into the 10.0.1 release, you still have about a month
to get your fix in. To request a patch be backported to the release/10.x branch,
file a bug and mark it as a blocker of the release-10.0.1 meta bug.
-Tom
Uploaded Ubuntu/Xubuntu 20.04.
sha256sum clang+llvm-10.0.1-rc1-x86_64-pc-linux-gnu.tar.xz
5145c89d788b1180d532101e6142b8c78424b6431e9376c41b02ebec776a8335
No Unexpected Failures.
Last two test results.
15 warning(s) in tests
Testing Time: 507.43s
Expected Passes : 67725
Expected Failures : 269
Unsupported Tests : 1946
[100%] Built target check-all
Testing Time: 157.04s
Expected Passes : 2404
[100%] Built target check
Neil Nelson
Windows looks good. Uploaded:
$ sha256sum LLVM-10.0.1-rc1-win*.exe
3ca57fc9b80c796a1a68f71a60d94cd5f94818b2b326efaf4e558228565cbecc
LLVM-10.0.1-rc1-win32.exe
ada2f4d596259fad9dd9efa4a14999462feb259dbecd1b7b387539d853f640f3
LLVM-10.0.1-rc1-win64.exe
They were built with the attached batch. file.
- Hans
build_llvm_1001-rc1.bat|attachment (4.88 KB)
macOS builds are up - a few tests are failing:
FAIL: LLVM :: Bindings/Go/go.test (25250 of 67087)
FAIL: ThreadSanitizer-x86_64 :: Darwin/norace-objcxx-run-time.mm
(57256 of 67087)
FAIL: libunwind :: signal_frame.pass.cpp (64790 of 67087)
none of these seems new to me.
SHA256:a98f882ee94f4b22832e9da3639f1a962bb0edc1046d975c55b7c10c27d5c946
Hello,
I finished testing llvm-10.0.1 RC1 on Power PC 64bit Little Endian Ubuntu 16.04 machine and have uploaded the binary from IBM.
There were no regressions. The sha1 file is attached.
Thanks,
Anil Mahmud.
clang+llvm-10.0.1-rc1-powerpc64le-linux-ubuntu-16.04.sha1 (102 Bytes)
Hello,
I finished testing llvm-10.0.1 RC1 on Power PC 64bit Little Endian Red Hat 7.4 machine and have uploaded the binary from IBM.
There were no regressions. The sha1 file is attached.
Thanks,
Anil Mahmud
clang+llvm-10.0.1-rc1-powerpc64le-linux-rhel-7.4.sha1 (98 Bytes)
Thanks a lot. Just out of curiosity regarding 10.0.1, will it somehow
address the 7%-8% of performance loss that some users reported, or
will that be postponed to 11.0.0?
Thanks a lot. Just out of curiosity regarding 10.0.1, will it somehow
address the 7%-8% of performance loss that some users reported, or
will that be postponed to 11.0.0?
I don't know yet, there is still 1 month left of 10.0.1 stabilization.
Someone would need to pinpoint the issues and propose a fix for it.
-Tom
I have uploaded:
SHA256 (clang+llvm-10.0.1-rc1-amd64-unknown-freebsd11.tar.xz) = 4dbe2041e8aa80ba2b908946052bd4bb20733422707277aa7c297980ed8cd92c
SHA256 (clang+llvm-10.0.1-rc1-i386-unknown-freebsd11.tar.xz) = 5fad007fdabe085de126513875a8e601b1f341889eb36423d2980dd3d34b1d80
but none of the regression tests could run, due to a lit/googletest exception:
llvm-lit: /home/dim/llvm/10.0.1/rc1/llvm-project/llvm/utils/lit/lit/formats/googletest.py:43: warning: unable to discover google-tests in '/home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests': Command '['/home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests', '--gtest_list_tests']' returned non-zero exit status 1.. Process output: b''
Traceback (most recent call last):
File "/home/dim/llvm/10.0.1/rc1/llvm-project/llvm/utils/lit/lit/formats/googletest.py", line 39, in getGTestTests
env=localConfig.environment)
File "/usr/local/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
File "/usr/local/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests', '--gtest_list_tests']' returned non-zero exit status 1.
Running the MLIRSPIRVTests executable shows the actual problem:
$ /home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests
Shared object "libc++abi.so.1" not found, required by "MLIRSPIRVTests"
On FreeBSD we use libcxxrt, not libc++abi. Does anybody have an idea why this appears to have changed between 10.0.0 and 10.0.1? And if so, how I tell the build not to link against libc++abi?
-Dimitry
Just FYI, the sky seems to have fallen on me here. I'm not really sure
why it worked before but a lot of parts of clang fail now due to
duplicate registered command-line options. I will file bugs when I'm
done figuring out all the fixes but giving you an early heads-up.
Ok, it turns out my issues were due to py3.7+. I've requested
backporting one lit patch and with it, there are no new regressions.
However, it made me notice that some clangd unittest are failing to
execute with duplicate command-line option errors but the errors are
ignored by lit. It happens when clang is linked to dylib, and it is
non-trivial to fix and I'm not sure if I'll be able to fix it myself.
Any and all help appreciated.
I've tried to see if it is fixed in master but I can't seem to manage to
find a recent clang revision that wouldn't segfault all the way.
Hi,
Uploaded binaries for ARM & AArch64:
e7cdf76722c9f5b90ec3f5d0e6cf5545badc6a7eaf8477b764a25845aee9a844 clang+llvm-10.0.1-rc1-aarch64-linux-gnu.tar.xz
a11427f38283a522a22f4799c40518b09b72bdd4170ecb456544b459f74d1fc3 clang+llvm-10.0.1-rc1-armv7a-linux-gnueabihf.tar.xz
AArch64 is green (yay! IIRC 10.0.0 had an issue).
For ARM we still have PR44157 & PR44158 (which we also had for llvm 10.0.0), and I have also opened PR46092 and PR46093 for some new failures. I’ll try to have a quick look to see if they’re environment problems or if we can bisect them.
Cheers,
Diana
Hi,
In this release as well as the 10.0.0 release, llvm fails to build on Windows with the latest Visual Studio version (16.6.0) when building for debug.
See LLVM not building in Vusual Studio - #3 by jcmac - Beginners - LLVM Discussion Forums
Something seems to go wrong with the debug build of llvm-tblgen.exe
This problem does not exist on the current master branch.
Machiel
Hi,
In this release as well as the 10.0.0 release, llvm fails to build on Windows with the latest Visual Studio version (16.6.0) when building for debug.
See LLVM not building in Vusual Studio - #3 by jcmac - Beginners - LLVM Discussion Forums
Can you file a bug for this?
-Tom
Does https://reviews.llvm.org/D80433 look related?
Hi,
In this release as well as the 10.0.0 release, llvm fails to build on
Windows with the latest Visual Studio version (16.6.0) when building for
debug.
See LLVM not building in Vusual Studio - #3 by jcmac - Beginners - LLVM Discussion Forums
Something seems to go wrong with the debug build of llvm-tblgen.exe
This problem does not exist on the current master branch.
Machiel