[7.0.0 Release] rc3 has been tagged

Hans_Wennborg · September 10, 2018, 2:12pm

Dear testers,

7.0.0-rc3 was just tagged (from branch revision r341805).

No further release candidates are currently planned, so this is a
release candidate in the real sense: unless any serious issues
surface, this is what the final release will look like.

Please run the test script, share your results and upload binaries.

Please also take a look at the release notes and other docs; small
changes to those are still welcome.

The sources and docs will show up at
https://prereleases.llvm.org/7.0.0/#rc3 anytime now, and binaries will
be posted when they're ready.

Thanks everyone for your work on this release!

Hans

hahnjo · September 10, 2018, 3:49pm

Builds and tests successfully with a custom install script. As I mentioned for rc1, I'm now skipping lldb because it doesn't look maintained on Linux.

Thanks for the good work!
Jonas

Andrew_Kelley1 · September 10, 2018, 4:34pm

Is LLVM not doing the “List of external projects” section anymore?

Looks like this didn’t make it into the release notes:

https://reviews.llvm.org/D51118

Andres_Freund · September 10, 2018, 9:53pm

Hi,

Please also take a look at the release notes and other docs; small
changes to those are still welcome.

I don't quite know what the criteria are for the release notes (sorry,
still pretty new here). It might be worthwhile to mention two additional
things - but I'm certainly biased:
- Support for profiling JITed code with perf (r337789)
- Expanding the OrcJIT APIs exposed to C so they can register event
listeners like debuggers and profilers (r333227, r333228, r333229, r333230)

Greetings,

Andres Freund

jvesely · September 11, 2018, 3:08am

Hi,

do you mind updating the llvm.org webpage as well? It still states the old schedule of final release on Sept 5.

thanks,
Jan

Hans_Wennborg · September 11, 2018, 8:16am

We do. Sorry, I had just forgotten to commit your patch. It's been
committed now.

Hans_Wennborg · September 11, 2018, 8:16am

Updated now. Thanks for the reminder!

Hans_Wennborg · September 11, 2018, 8:40am

Added in r341916. Thanks!

DimitryAndric · September 11, 2018, 9:21am

Main test results on amd64-freebsd11 look slightly better, 2 less unexpected failures:

  Expected Passes : 52422 (rc2: 52409)
  Expected Failures : 232 (rc2: 232)
  Unsupported Tests : 3687 (rc2: 3687)
  Unexpected Passes : 1 (rc2: 1)
  Unexpected Failures: 489 (rc2: 491)

Test-suite test results on amd64-freebsd11 are also better, 58 less unexpected failures:

Expected Passes : 903 (rc2: 845)
Unexpected Failures: 3 (rc2: 61)

Test results on i386-freebsd11 were slightly worse, due to a bunch of hanging lldb single step tests (these all seem to hang in the STOP state indefinitely, and so had to be killed off):

  Expected Passes : 50226 (rc2: 50186)
  Expected Failures : 226 (rc2: 226)
  Unsupported Tests : 2502 (rc2: 2502)
  Unexpected Failures: 277 (rc2: 306)

The test-suite still doesn't build on i386-freebsd, but that is a known issue.

I have uploaded:

SHA256 (clang+llvm-7.0.0-rc3-amd64-unknown-freebsd11.tar.xz) = 1b5d72f94e4f18713393ad0ce4f1509ee13b8b41fde114e9a18b2247e2a740cb
SHA256 (clang+llvm-7.0.0-rc3-i386-unknown-freebsd11.tar.xz) = 4e09e6a9d06982ba35b6e213d74498c9b46b01bfd044728d6f81de50791dbd4a

-Dimitry

Hans_Wennborg · September 11, 2018, 11:35am

Windows looks good:

$ sha1sum LLVM-7.0.0-rc3*.exe
1e5f9b697703913ee643cfb826abb5f1164d4800 LLVM-7.0.0-rc3-win32.exe
bb3d4a5c102d0aca8b8f2d0e55ba56899f3ee821 LLVM-7.0.0-rc3-win64.exe

build_llvm_700-rc3.bat|attachment (4.09 KB)

mgorny · September 11, 2018, 4:06pm

I see two regressions in compiler-rt since RC2:

Failing Tests (2):
LeakSanitizer-AddressSanitizer-i386 :: TestCases/Linux/fork_and_leak.cc
LeakSanitizer-Standalone-i386 :: TestCases/Linux/fork_and_leak.cc

Besides that, nothing new to report.

Bernhard_Rosenkranze · September 12, 2018, 12:56am

Hi,
OpenMandriva is updated and runs well, so far we've found one problem
while rebuilding the OS with rc3:

http://file-store.openmandriva.org/api/v1/file_stores/e95b2bd9e6e7dfcfbbab1906d20763879fa6f489.log?show=true

Building libqalculate on armv7hnl causes the compiler to barf. I
didn't get around to debugging this yet. Same package builds ok on all
other supported arches (aarch64, x86_64, i686).

ttyl
bero

kraj · September 12, 2018, 1:08am

Dear testers,

7.0.0-rc3 was just tagged (from branch revision r341805).

No further release candidates are currently planned, so this is a
release candidate in the real sense: unless any serious issues
surface, this is what the final release will look like.

Please run the test script, share your results and upload binaries.

There is one build failure on Yocto armv7l/rpi3

http://errors.yoctoproject.org/Errors/Details/192518/

This problem has been reported in older releases as well. I have but
iit is showing up in ruby in 7.0+ updated the status in
https://bugs.llvm.org/show_bug.cgi?id=28629

Bjoern_Gaier · September 12, 2018, 7:19am

Hello,

I'm sorry to write you, because I fear that I'm doing it wrong... or that it is nothing.
Yesterday I downloaded the LLVM7rc3 - with the files for LLVM, Clang, compiler-rt and LLD.

I used CMake to generate me a VisualStudio2017 solution. Compiling is no problem, but when running "Install" compiler-rt has some problems. I attach the output:

88>-- Up-to-date: C:/Program Files/LLVM7/lib/clang/7.0.0/include/xray/xray_log_interface.h
88>CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file):
88> file INSTALL cannot find
88> "D:/Users/h16020/Desktop/Clang_LLVM/Source/LLVM7/CMake/$(Configuration)/lib/clang/7.0.0/lib/windows/clang_rt.builtins-x86_64.lib".
88>Call Stack (most recent call first):
88> projects/compiler-rt/lib/cmake_install.cmake:33 (include)
88> projects/compiler-rt/cmake_install.cmake:33 (include)
88> projects/cmake_install.cmake:32 (include)
88> cmake_install.cmake:58 (include)
88>
88>
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: The command "setlocal
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P cmake_install.cmake
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmErrorLevel
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd
88>D:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" exited with code 1.
88>Done building project "INSTALL.vcxproj" -- FAILED.
========== Build: 87 succeeded, 1 failed, 320 up-to-date, 0 skipped ==========

I take the problem is the line "88> "D:/Users/h16020/Desktop/Clang_LLVM/Source/LLVM7/CMake/$(Configuration)/lib/clang/7.0.0/lib/windows/clang_rt.builtins-x86_64.lib"." cause the value $(Configuration) was not replaced with "Release". I think that VisualStudio should do that... The files does exist by the way!

Ehm... So I have really no idea if this was helpful or not...But I though I should share it...

Sorry and kind greetings
Björn

Hans_Wennborg · September 12, 2018, 11:57am

Can you please file a bug (blocking PR38406) with the preprocessed
source and invocation attached (/tmp/MathStructure-619267.cpp and
/tmp/MathStructure-619267.sh as mentioned in the output you linked
to)?

Did the same project build successfully with the previous release candidates?

Thanks,
Hans

androm3da · September 12, 2018, 1:31pm

Uploaded sles binaries.

ba4e93b281bc53372cea22da624c02dad566a7b6 clang+llvm-7.0.0-rc3-x86_64-linux-sles11.3.tar.xz
d3cbc4a96adbfd5480601bd6a9faf62879976cf8 clang+llvm-7.0.0-rc3-x86_64-linux-sles12.3.tar.xz

Sylvestre_Ledru · September 12, 2018, 1:34pm

Works great on the most important platforms on Debian.

Nothing new compare to rc2 for now
S

chapuni · September 12, 2018, 2:02pm

FYI, CentOS6 RPMs are here;
https://github.com/llvm-project/llvm-project-20170507/releases/tag/RELEASE_700%2Frc3

Hans_Wennborg · September 13, 2018, 9:06am

This has been reported before:
https://groups.google.com/d/msg/llvm-dev/N7E78xf9w70/eBIehWiOBgAJ
So I don't think you're doing anything wrong, and it's not a recent regression.

I wasn't able to reproduce this (wasn't able to get the build to work
with msbuild at all actually), but as a work-around I suggest using
Ninja (https://ninja-build.org/) instead. It will also make your build
significantly faster.

Hans_Wennborg · September 13, 2018, 12:18pm

Did you have time to look into this yet? So far this sounds like the
only real blocker for the release, but it's hard to assess without a
reproducer.