thr3ads.net - llvm dev - [llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here [Feb 2020]

If this information is useful, please help other people find it:
Share via:

Hans Wennborg via llvm-dev

2020-Jan-30 19:38 UTC

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Hello everyone,

It took a bit longer than planned due to master being a somewhat
unstable at the branch point, but Release Candidate 1 has now been
tagged as llvmorg-10.0.0-rc1.

Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc1

Pre-built binaries will be added there as they become available.

Please file bug reports for any issues you find as blockers of
https://llvm.org/pr44555

Release testers: please start your engines, run the script, share your
results, and upload binaries.

Release Candidate 2 was previously scheduled for February 2. Because
of the late RC1, I've pushed this back a bit to the 11th.

Thanks,
Hans

MyDeveloper Day via llvm-dev

2020-Jan-31 08:49 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Would it be possible to get an update of the Windows snapshot builds to
build 11.0  https://llvm.org/builds/

Thanks in advance

@MyDeveloperDay

On Thu, Jan 30, 2020 at 7:39 PM Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello everyone,
>
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
>
> Source code and docs are available at
> https://prereleases.llvm.org/10.0.0/#rc1
>
> Pre-built binaries will be added there as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> Release Candidate 2 was previously scheduled for February 2. Because
> of the late RC1, I've pushed this back a bit to the 11th.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/f5d93e11/attachment.html>

Dimitry Andric via llvm-dev

2020-Jan-31 20:36 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <release-testers
at lists.llvm.org> wrote:> 
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
For this rc, I used three patches, which are attached.

Main results on amd64-freebsd11 (I will post i386 results as they become
available):

  Expected Passes    : 67894
  Expected Failures  : 268
  Unsupported Tests  : 4653
  Unexpected Passes  : 5
  Unexpected Failures: 541
  Individual Timeouts: 18

Uploaded:
SHA256 (clang+llvm-10.0.0-rc1-amd64-unknown-freebsd11.tar.xz) =
751f2d86eede35a201db524a78ebb0e9d48b71d120b44153f961edb666d30c96

Unfortunately the test-suite did not build at all, as all the Bitcode
compilations failed with segfaults, similar to the following run under
gdb:

Starting program:
/home/dim/llvm/10.0.0/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin/clang++
-DNDEBUG -O3 -DNDEBUG -w -Werror=date-time -std=c++11 -MD -MT
Bitcode/Benchmarks/Halide/local_laplacian/CMakeFiles/halide_local_laplacian.dir/__/common/x86_halide_runtime.bc.o
-MF
Bitcode/Benchmarks/Halide/local_laplacian/CMakeFiles/halide_local_laplacian.dir/__/common/x86_halide_runtime.bc.o.d
-o
Bitcode/Benchmarks/Halide/local_laplacian/CMakeFiles/halide_local_laplacian.dir/__/common/x86_halide_runtime.bc.o
-c
/home/dim/llvm/10.0.0/rc1/llvm-test-suite/Bitcode/Benchmarks/Halide/common/x86_halide_runtime.bc

Program received signal SIGSEGV, Segmentation fault.
0x000000010000000f in ?? ()
(gdb) bt
#0  0x000000010000000f in ?? ()
#1  0x00000000028ca9c0 in
llvm::AAResultsWrapperPass::runOnFunction(llvm::Function&) ()
#2  0x0000000002e8edc0 in
llvm::FPPassManager::runOnFunction(llvm::Function&) ()
#3  0x0000000002e8f1d3 in llvm::FPPassManager::runOnModule(llvm::Module&) ()
#4  0x0000000002e8f6a9 in llvm::legacy::PassManagerImpl::run(llvm::Module&)
()
#5  0x00000000035de7dc in
clang::EmitBackendOutput(clang::DiagnosticsEngine&,
clang::HeaderSearchOptions const&, clang::CodeGenOptions const&,
clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout
const&, llvm::Module*, clang::BackendAction,
std::__1::unique_ptr<llvm::raw_pwrite_stream,
std::__1::default_delete<llvm::raw_pwrite_stream> >) ()
#6  0x0000000003c17e67 in clang::CodeGenAction::ExecuteAction() ()
#7  0x0000000003b7abca in clang::FrontendAction::Execute() ()
#8  0x0000000003aea761 in
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) ()
#9  0x0000000003c12905 in
clang::ExecuteCompilerInvocation(clang::CompilerInstance*) ()
#10 0x0000000001cbaf0e in cc1_main(llvm::ArrayRef<char const*>, char
const*, void*) ()
#11 0x0000000001cb8f65 in ExecuteCC1Tool(llvm::SmallVectorImpl<char
const*>&) ()
#12 0x00000000039eb297 in void llvm::function_ref<void
()>::callback_fn<clang::driver::CC1Command::Execute(llvm::ArrayRef<llvm::Optional<llvm::StringRef>
>, std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >*, bool*) const::$_1>(long) ()
#13 0x00000000033e406a in
llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>) ()
#14 0x00000000039ea7f0 in
clang::driver::CC1Command::Execute(llvm::ArrayRef<llvm::Optional<llvm::StringRef>
>, std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >*, bool*) const ()
#15 0x00000000039bfc5c in
clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&,
clang::driver::Command const*&) const ()
#16 0x00000000039c01ac in
clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&,
llvm::SmallVectorImpl<std::__1::pair<int, clang::driver::Command
const*> >&) const ()
#17 0x00000000039d336c in
clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&,
llvm::SmallVectorImpl<std::__1::pair<int, clang::driver::Command
const*> >&) ()
#18 0x0000000001cb884f in main ()

Looks like the bitcode compilation path is totally busted?  Anybody know
an open bug for this?

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-clang-1.diff
Type: application/octet-stream
Size: 447 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/93e7f485/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-compiler-rt-1.diff
Type: application/octet-stream
Size: 890 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/93e7f485/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-test-suite-1.diff
Type: application/octet-stream
Size: 552 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/93e7f485/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/93e7f485/attachment.sig>

Michał Górny via llvm-dev

2020-Jan-31 20:51 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On Thu, 2020-01-30 at 14:38 -0500, Hans Wennborg via Release-testers
wrote:> Please file bug reports for any issues you find as blockers
of> https://llvm.org/pr44555
> 
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
> 
Gentoo/amd64 issues (with 32-bit multilib where available):

- libc++ stand-alone builds were broken; revert was committed
  as 3573526c028;  with that patch, all tests pass for me.

- there's one openmp issue on 32-bit build:
  https://bugs.llvm.org/show_bug.cgi?id=44733
  
- I've found an LLDB bug with linking liblldb.so in tests.
  I don't think it's strictly a regression but I don't recall
noticing
  it before.  I've started working on a patch:
  https://reviews.llvm.org/D73767

  However, I'm not sure if it's worth backporting.  There's still
  a plethora of failing tests, plus some lit bug causing it to hang
  at the end, and I don't think I'll find time to look into any of this
  anytime soon.

-- 
Best regards,
Michał Górny

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/35c10981/attachment.sig>

Neil Nelson via llvm-dev

2020-Feb-01 06:30 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Obtained the following error for Xubuntu/Ubuntu 19.10.

Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.
FAIL: LLVM :: tools/llvm-ar/quick-append.test (53134 of 69456)
******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' 
FAILED ********************
Script:
--
: 'RUN: at line 3';   rm -rf 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp
&& mkdir -p 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp
: 'RUN: at line 4'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/yaml2obj
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
-o 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
--docnum=1
: 'RUN: at line 5'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/yaml2obj
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
-o 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
--docnum=2
: 'RUN: at line 8'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qc 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 9'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
t 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=SINGLE --match-full-lines --implicit-check-not {{.}}
: 'RUN: at line 14'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm
--print-armap 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=SINGLE-SYM
: 'RUN: at line 20'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qc 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
: 'RUN: at line 21'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
t 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=MULTIPLE --match-full-lines --implicit-check-not {{.}}
: 'RUN: at line 27'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm
--print-armap 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=MULTIPLE-SYM
: 'RUN: at line 34'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qc 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 35'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
t 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=SAME 
-DFILE=/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
--match-full-lines --implicit-check-not {{.}}
: 'RUN: at line 41'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm
--print-armap 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=SAME-SYM
: 'RUN: at line 48'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qc 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
: 'RUN: at line 49'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
t 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/count
0
: 'RUN: at line 51'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm
--print-armap 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/count
0
: 'RUN: at line 54';   not 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qc 2>&1    | 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=NO-ARCHIVE
: 'RUN: at line 60';   not 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qc 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.txt
2>&1    | 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=MISSING-FILE 
-DFILE=/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.txt
: 'RUN: at line 66'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qcT 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 67'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qcT 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
: 'RUN: at line 68'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
t 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=MULTIPLE
: 'RUN: at line 71'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
qcT 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-same.a
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 72'; 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar
t 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-same.a
| 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test
--check-prefix=SAME
--
Exit Code: 1

Command Output (stderr):
--
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test:39:14:
error: SAME-NEXT: is on the same line as previous match
# SAME-NEXT: 1.o
              ^
<stdin>:1:148: note: 'next' match was here
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
^
<stdin>:1:97: note: previous match ended here
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
^

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..

15 warning(s) in tests

Testing Time: 702.88s
********************
Failing Tests (1):
     LLVM :: tools/llvm-ar/quick-append.test

   Expected Passes    : 66539
   Expected Failures  : 267
   Unsupported Tests  : 2649
   Unexpected Failures: 1
make[3]: *** [CMakeFiles/check-all.dir/build.make:58: 
CMakeFiles/check-all] Error 1
make[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of 
errors.
make[2]: *** [CMakeFiles/Makefile2:358: CMakeFiles/check-all.dir/all] 
Error 2
make[1]: *** [CMakeFiles/Makefile2:365: CMakeFiles/check-all.dir/rule] 
Error 2
make[1]: Target 'check-all' not remade because of errors.
make: *** [Makefile:238: check-all] Error 2

Neil Nelson

On 1/30/20 12:38 PM, Hans Wennborg via llvm-dev wrote:> Hello everyone,
>
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
>
> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
>
> Pre-built binaries will be added there as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> Release Candidate 2 was previously scheduled for February 2. Because
> of the late RC1, I've pushed this back a bit to the 11th.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200131/ccd996d2/attachment-0001.html>

Hans Wennborg via llvm-dev

2020-Feb-03 09:37 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

On Thu, Jan 30, 2020 at 8:38 PM Hans Wennborg <hans at chromium.org>
wrote:>
> Hello everyone,
>
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
>
> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
>
> Pre-built binaries will be added there as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
Windows is ready:

$ sha256sum LLVM-10.0.0-rc1-win*.exe
d7d7e51c1b972b071222fb377cc8f828a43030c8bef7530a7b59a8b78126c657
LLVM-10.0.0-rc1-win32.exe
858c4cd712e89be723f5ed9366758e6d759bc0a71f557dce1580a28a61c1fe3e
LLVM-10.0.0-rc1-win64.exe

They were built with the attached batch file.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build_llvm_1000-rc1._bat_
Type: application/octet-stream
Size: 4695 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200203/cb8533df/attachment.obj>

Hans Wennborg via llvm-dev

2020-Feb-03 09:57 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On Fri, Jan 31, 2020 at 9:37 PM Dimitry Andric <dimitry at andric.com>
wrote:>
> On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
> >
> > It took a bit longer than planned due to master being a somewhat
> > unstable at the branch point, but Release Candidate 1 has now been
> > tagged as llvmorg-10.0.0-rc1.
>
> For this rc, I used three patches, which are attached.
>
> Main results on amd64-freebsd11 (I will post i386 results as they become
> available):
>
>   Expected Passes    : 67894
>   Expected Failures  : 268
>   Unsupported Tests  : 4653
>   Unexpected Passes  : 5
>   Unexpected Failures: 541
>   Individual Timeouts: 18
>
> Uploaded:
> SHA256 (clang+llvm-10.0.0-rc1-amd64-unknown-freebsd11.tar.xz) =
751f2d86eede35a201db524a78ebb0e9d48b71d120b44153f961edb666d30c96
Thanks! I've added it to the pre-release page and also to the github
release.
>
> Unfortunately the test-suite did not build at all, as all the Bitcode
> compilations failed with segfaults, similar to the following run under
> gdb:
>
> Starting program:
/home/dim/llvm/10.0.0/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin/clang++
-DNDEBUG -O3 -DNDEBUG -w -Werror=date-time -std=c++11 -MD -MT
Bitcode/Benchmarks/Halide/local_laplacian/CMakeFiles/halide_local_laplacian.dir/__/common/x86_halide_runtime.bc.o
-MF
Bitcode/Benchmarks/Halide/local_laplacian/CMakeFiles/halide_local_laplacian.dir/__/common/x86_halide_runtime.bc.o.d
-o
Bitcode/Benchmarks/Halide/local_laplacian/CMakeFiles/halide_local_laplacian.dir/__/common/x86_halide_runtime.bc.o
-c
/home/dim/llvm/10.0.0/rc1/llvm-test-suite/Bitcode/Benchmarks/Halide/common/x86_halide_runtime.bc
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000010000000f in ?? ()
> (gdb) bt
> #0  0x000000010000000f in ?? ()
> #1  0x00000000028ca9c0 in
llvm::AAResultsWrapperPass::runOnFunction(llvm::Function&) ()
> #2  0x0000000002e8edc0 in
llvm::FPPassManager::runOnFunction(llvm::Function&) ()
> #3  0x0000000002e8f1d3 in
llvm::FPPassManager::runOnModule(llvm::Module&) ()
> #4  0x0000000002e8f6a9 in
llvm::legacy::PassManagerImpl::run(llvm::Module&) ()
> #5  0x00000000035de7dc in
clang::EmitBackendOutput(clang::DiagnosticsEngine&,
clang::HeaderSearchOptions const&, clang::CodeGenOptions const&,
clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout
const&, llvm::Module*, clang::BackendAction,
std::__1::unique_ptr<llvm::raw_pwrite_stream,
std::__1::default_delete<llvm::raw_pwrite_stream> >) ()
> #6  0x0000000003c17e67 in clang::CodeGenAction::ExecuteAction() ()
> #7  0x0000000003b7abca in clang::FrontendAction::Execute() ()
> #8  0x0000000003aea761 in
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) ()
> #9  0x0000000003c12905 in
clang::ExecuteCompilerInvocation(clang::CompilerInstance*) ()
> #10 0x0000000001cbaf0e in cc1_main(llvm::ArrayRef<char const*>, char
const*, void*) ()
> #11 0x0000000001cb8f65 in ExecuteCC1Tool(llvm::SmallVectorImpl<char
const*>&) ()
> #12 0x00000000039eb297 in void llvm::function_ref<void
()>::callback_fn<clang::driver::CC1Command::Execute(llvm::ArrayRef<llvm::Optional<llvm::StringRef>
>, std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >*, bool*) const::$_1>(long) ()
> #13 0x00000000033e406a in
llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>) ()
> #14 0x00000000039ea7f0 in
clang::driver::CC1Command::Execute(llvm::ArrayRef<llvm::Optional<llvm::StringRef>
>, std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >*, bool*) const ()
> #15 0x00000000039bfc5c in
clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&,
clang::driver::Command const*&) const ()
> #16 0x00000000039c01ac in
clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&,
llvm::SmallVectorImpl<std::__1::pair<int, clang::driver::Command
const*> >&) const ()
> #17 0x00000000039d336c in
clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&,
llvm::SmallVectorImpl<std::__1::pair<int, clang::driver::Command
const*> >&) ()
> #18 0x0000000001cb884f in main ()
>
> Looks like the bitcode compilation path is totally busted?  Anybody know
> an open bug for this?
I haven't seen one, but I'm behind on email. Can you please file one
to make sure this gets tracked?

Thanks,
Hans

Hans Wennborg via llvm-dev

2020-Feb-03 10:07 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On Fri, Jan 31, 2020 at 9:51 PM Michał Górny <mgorny at gentoo.org>
wrote:>
> On Thu, 2020-01-30 at 14:38 -0500, Hans Wennborg via Release-testers
> wrote:
> >
> Please file bug reports for any issues you find as blockers of
> > https://llvm.org/pr44555
> >
> > Release testers: please start your engines, run the script, share your
> > results, and upload binaries.
> >
>
> Gentoo/amd64 issues (with 32-bit multilib where available):
>
> - libc++ stand-alone builds were broken; revert was committed
>   as 3573526c028;  with that patch, all tests pass for me.
>
> - there's one openmp issue on 32-bit build:
>   https://bugs.llvm.org/show_bug.cgi?id=44733
>
> - I've found an LLDB bug with linking liblldb.so in tests.
>   I don't think it's strictly a regression but I don't recall
noticing
>   it before.  I've started working on a patch:
>   https://reviews.llvm.org/D73767
>
>   However, I'm not sure if it's worth backporting.  There's
still
>   a plethora of failing tests, plus some lit bug causing it to hang
>   at the end, and I don't think I'll find time to look into any of
this
>   anytime soon.
Thanks for digging into these issues!

Hans Wennborg via llvm-dev

2020-Feb-03 10:39 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

On Sat, Feb 1, 2020 at 7:30 AM Neil Nelson via llvm-dev
<llvm-dev at lists.llvm.org> wrote:>
> Obtained the following error for Xubuntu/Ubuntu 19.10.
>
> Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.
> FAIL: LLVM :: tools/llvm-ar/quick-append.test (53134 of 69456)
> ******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test'
FAILED ********************
[...]> Command Output (stderr):
> --
>
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test:39:14:
error: SAME-NEXT: is on the same line as previous match
> # SAME-NEXT: 1.o
>              ^
> <stdin>:1:148: note: 'next' match was here
>
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
>                                                                            
^
> <stdin>:1:97: note: previous match ended here
>
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
>                                                                            
^
Looks like the test is confused about the "1.o" part of the
"...-rc1.obj" build directory.

I've fixed that in f00ab188f4e4214dfbecfdd8968a183e9363cefa and
cherry-picked to the branch in
e11d70cfe7e2a8537eb774ed1780e9ecd1aa90a0

Hans Wennborg via llvm-dev

2020-Feb-03 14:38 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Yes, I've just pushed a new one based on 2663a25f: http://llvm.org/builds/

On Fri, Jan 31, 2020 at 9:49 AM MyDeveloper Day
<mydeveloperday at gmail.com> wrote:>
> Would it be possible to get an update of the Windows snapshot builds to
build 11.0  https://llvm.org/builds/
>
> Thanks in advance
>
> @MyDeveloperDay
>
> On Thu, Jan 30, 2020 at 7:39 PM Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>>
>> Hello everyone,
>>
>> It took a bit longer than planned due to master being a somewhat
>> unstable at the branch point, but Release Candidate 1 has now been
>> tagged as llvmorg-10.0.0-rc1.
>>
>> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
>>
>> Pre-built binaries will be added there as they become available.
>>
>> Please file bug reports for any issues you find as blockers of
>> https://llvm.org/pr44555
>>
>> Release testers: please start your engines, run the script, share your
>> results, and upload binaries.
>>
>> Release Candidate 2 was previously scheduled for February 2. Because
>> of the late RC1, I've pushed this back a bit to the 11th.
>>
>> Thanks,
>> Hans
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Tobias Hieta via llvm-dev

2020-Feb-03 19:52 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hello,

A little late but macOS built with the following test errors:

FAIL: LLVM :: Bindings/Go/go.test (25649 of 67018)
FAIL: LLVM :: tools/llvm-ar/quick-append.test (52450 of 67018)
FAIL: Profile-x86_64 :: ContinuousSyncMode/online-merging.c (56222 of 67018)
FAIL: ThreadSanitizer-x86_64 :: Darwin/norace-objcxx-run-time.mm
(57192 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/except.nested/assign.pass.cpp
(60964 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/except.nested/ctor_copy.pass.cpp
(60965 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/except.nested/ctor_default.pass.cpp
(60966 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/except.nested/rethrow_if_nested.pass.cpp
(60967 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/except.nested/rethrow_nested.pass.cpp
(60968 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/propagation/make_exception_ptr.pass.cpp
(60978 of 67018)
FAIL: libc++ ::
std/language.support/support.exception/propagation/rethrow_exception.pass.cpp
(60979 of 67018)
FAIL: libc++ :: std/thread/futures/futures.promise/dtor.pass.cpp
(62964 of 67018)
FAIL: libc++ ::
std/thread/futures/futures.promise/set_exception.pass.cpp (62967 of
67018)
FAIL: libc++ ::
std/thread/futures/futures.promise/set_exception_at_thread_exit.pass.cpp
(62969 of 67018)
FAIL: libc++ :: std/thread/futures/futures.async/async.pass.cpp (62991 of 67018)
FAIL: libc++ :: std/thread/futures/futures.shared_future/get.pass.cpp
(62997 of 67018)
FAIL: libc++ ::
std/thread/futures/futures.task/futures.task.members/dtor.pass.cpp
(63003 of 67018)
FAIL: libc++ ::
std/thread/futures/futures.task/futures.task.members/make_ready_at_thread_exit.pass.cpp
(63014 of 67018)
FAIL: libc++ ::
std/thread/futures/futures.task/futures.task.members/operator.pass.cpp
(63015 of 67018)
FAIL: libc++ :: std/thread/futures/futures.unique_future/get.pass.cpp
(63024 of 67018)
FAIL: libunwind :: signal_frame.pass.cpp (64734 of 67018)

That seems to be a few more in there than 9.0.1.

I have uploaded to google drive (still no sftp access):
https://drive.google.com/open?id=1wPXrtRcxxPm29C5ZcwPJLfAXiFjFmCWK
SHA256: 904b9827f4980d311f8fdf1c33ad01aa64c79d99e8f8ef0798851104f9e019b1

On Thu, Jan 30, 2020 at 8:38 PM Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:>
> Hello everyone,
>
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
>
> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
>
> Pre-built binaries will be added there as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> Release Candidate 2 was previously scheduled for February 2. Because
> of the late RC1, I've pushed this back a bit to the 11th.
>
> Thanks,
> Hans
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

Hans Wennborg via llvm-dev

2020-Feb-04 10:28 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On Mon, Feb 3, 2020 at 8:52 PM Tobias Hieta <tobias at plexapp.com>
wrote:>
> Hello,
>
> A little late but macOS built with the following test errors:
>
> FAIL: LLVM :: Bindings/Go/go.test (25649 of 67018)
> FAIL: LLVM :: tools/llvm-ar/quick-append.test (52450 of 67018)
> FAIL: Profile-x86_64 :: ContinuousSyncMode/online-merging.c (56222 of
67018)
> FAIL: ThreadSanitizer-x86_64 :: Darwin/norace-objcxx-run-time.mm
> (57192 of 67018)
> FAIL: libc++ ::
> std/language.support/support.exception/except.nested/assign.pass.cpp
> (60964 of 67018)
> FAIL: libc++ ::
> std/language.support/support.exception/except.nested/ctor_copy.pass.cpp
> (60965 of 67018)
> FAIL: libc++ ::
> std/language.support/support.exception/except.nested/ctor_default.pass.cpp
> (60966 of 67018)
> FAIL: libc++ ::
>
std/language.support/support.exception/except.nested/rethrow_if_nested.pass.cpp
> (60967 of 67018)
> FAIL: libc++ ::
>
std/language.support/support.exception/except.nested/rethrow_nested.pass.cpp
> (60968 of 67018)
> FAIL: libc++ ::
>
std/language.support/support.exception/propagation/make_exception_ptr.pass.cpp
> (60978 of 67018)
> FAIL: libc++ ::
>
std/language.support/support.exception/propagation/rethrow_exception.pass.cpp
> (60979 of 67018)
> FAIL: libc++ :: std/thread/futures/futures.promise/dtor.pass.cpp
> (62964 of 67018)
> FAIL: libc++ ::
> std/thread/futures/futures.promise/set_exception.pass.cpp (62967 of
> 67018)
> FAIL: libc++ ::
> std/thread/futures/futures.promise/set_exception_at_thread_exit.pass.cpp
> (62969 of 67018)
> FAIL: libc++ :: std/thread/futures/futures.async/async.pass.cpp (62991 of
67018)
> FAIL: libc++ :: std/thread/futures/futures.shared_future/get.pass.cpp
> (62997 of 67018)
> FAIL: libc++ ::
> std/thread/futures/futures.task/futures.task.members/dtor.pass.cpp
> (63003 of 67018)
> FAIL: libc++ ::
>
std/thread/futures/futures.task/futures.task.members/make_ready_at_thread_exit.pass.cpp
> (63014 of 67018)
> FAIL: libc++ ::
> std/thread/futures/futures.task/futures.task.members/operator.pass.cpp
> (63015 of 67018)
> FAIL: libc++ :: std/thread/futures/futures.unique_future/get.pass.cpp
> (63024 of 67018)
> FAIL: libunwind :: signal_frame.pass.cpp (64734 of 67018)
>
> That seems to be a few more in there than 9.0.1.
>
> I have uploaded to google drive (still no sftp access):
> https://drive.google.com/open?id=1wPXrtRcxxPm29C5ZcwPJLfAXiFjFmCWK
> SHA256: 904b9827f4980d311f8fdf1c33ad01aa64c79d99e8f8ef0798851104f9e019b1
Thanks! I've added this to the pre-release page and to github.

Dimitry Andric via llvm-dev

2020-Feb-04 11:06 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <release-testers
at lists.llvm.org> wrote:> 
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
I tried building rc1 for 32-bit FreeBSD, but ran into a compile error in mlir:

/home/dim/llvm/10.0.0/rc1/llvm-project/mlir/lib/Transforms/DialectConversion.cpp:787:67:
error: non-constant-expression cannot be narrowed from type 'unsigned
int' to 'Region::iterator::difference_type' (aka 'int') in
initializer list [-Wc++11-narrowing]
    blockActions.push_back(BlockAction::getMove(&block, {&region,
position}));
                                                                  ^~~~~~~~
/home/dim/llvm/10.0.0/rc1/llvm-project/mlir/lib/Transforms/DialectConversion.cpp:787:67:
note: insert an explicit cast to silence this issue
    blockActions.push_back(BlockAction::getMove(&block, {&region,
position}));
                                                                  ^~~~~~~~
                                                                 
static_cast<difference_type>( )
1 error generated.

I submitted https://bugs.llvm.org/show_bug.cgi?id=44767 for this.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200204/019e6544/attachment.sig>

Anil Mahmud via llvm-dev

2020-Feb-05 20:00 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hello,

When running test-release.sh using GCC 5.4.0 we encountered this error :

/home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp:
In function ‘llvm::StringLiteral
clang::clangd::{anonymous}::getNameForExpr(const clang::Expr*)’:
/home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp:450:10:
error: could not convert ‘(const char*)"expression"’ from ‘const
char*’ to
‘llvm::StringLiteral’
   return "expression";
          ^

This was fixed by the  commit  40514a7d

commit 40514a7d7a3b745ba43c2d014e54a0d78d65d957
Author: Michael Liao <michael.hliao at gmail.com>
Date:   Thu Jan 16 16:02:47 2020 -0500

    [clangd] Add workaround for GCC5 host compilers. NFC.

diff --git a/clang-tools-extra/clangd/Hover.cpp
b/clang-tools-extra/clangd/Hover.cpp
index cfa5e3b..ad715db 100644
--- a/clang-tools-extra/clangd/Hover.cpp
+++ b/clang-tools-extra/clangd/Hover.cpp
@@ -439,7 +439,13 @@ bool isLiteral(const Expr *E) {

 llvm::StringLiteral getNameForExpr(const Expr *E) {
   // FIXME: Come up with names for `special` expressions.
-  return "expression";
+  //
+  // It's an known issue for GCC5, https://godbolt.org/z/Z_tbgi. Work
around
+  // that by using explicit conversion constructor.
+  //
+  // TODO: Once GCC5 is fully retired and not the minimal requirement as
stated
+  // in `GettingStarted`, please remove the explicit conversion
constructor.
+  return llvm::StringLiteral("expression");
 }

Can this be backported to RC1 10.0.0 ?

Thanks,
Anil Mahmud



On Tue, Feb 4, 2020 at 6:07 AM Dimitry Andric via Release-testers <
release-testers at lists.llvm.org> wrote:
> On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <
> release-testers at lists.llvm.org> wrote:
> >
> > It took a bit longer than planned due to master being a somewhat
> > unstable at the branch point, but Release Candidate 1 has now been
> > tagged as llvmorg-10.0.0-rc1.
>
> I tried building rc1 for 32-bit FreeBSD, but ran into a compile error in
> mlir:
>
>
/home/dim/llvm/10.0.0/rc1/llvm-project/mlir/lib/Transforms/DialectConversion.cpp:787:67:
> error: non-constant-expression cannot be narrowed from type 'unsigned
int'
> to 'Region::iterator::difference_type' (aka 'int') in
initializer list
> [-Wc++11-narrowing]
>     blockActions.push_back(BlockAction::getMove(&block, {&region,
> position}));
>                                                                   ^~~~~~~~
>
/home/dim/llvm/10.0.0/rc1/llvm-project/mlir/lib/Transforms/DialectConversion.cpp:787:67:
> note: insert an explicit cast to silence this issue
>     blockActions.push_back(BlockAction::getMove(&block, {&region,
> position}));
>                                                                   ^~~~~~~~
>
> static_cast<difference_type>( )
> 1 error generated.
>
> I submitted https://bugs.llvm.org/show_bug.cgi?id=44767 for this.
>
> -Dimitry
>
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200205/f6b7fa38/attachment.html>

Dimitry Andric via llvm-dev

2020-Feb-06 07:01 UTC

head link

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 4 Feb 2020, at 12:06, Dimitry Andric via Release-testers <release-testers
at lists.llvm.org> wrote:> 
> On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
>> 
>> It took a bit longer than planned due to master being a somewhat
>> unstable at the branch point, but Release Candidate 1 has now been
>> tagged as llvmorg-10.0.0-rc1.
> 
> I tried building rc1 for 32-bit FreeBSD, but ran into a compile error in
mlir:
For the i386 build of this rc, I used four patches, which are attached.

Main results on i386-freebsd11:

  Expected Passes    : 64948
  Expected Failures  : 251
  Unsupported Tests  : 3082
  Unresolved Tests   : 1
  Unexpected Passes  : 5
  Unexpected Failures: 232
  Individual Timeouts: 10

Uploaded:
SHA256 (clang+llvm-10.0.0-rc1-i386-unknown-freebsd11.tar.xz) =
2ae94f692d58ecc6833c76a809d2aa4fbc35d597ba7be355f2d15aef10d8b6db

Building the test-suite results in the same segfaults as on amd64, which
is tracked in https://bugs.llvm.org/show_bug.cgi?id=44763.

Note that the test-suite never fully built on i386 anyway, due to its
hardcoded use of SSE instructions, so this is not really a big
regression. :-)

-Dimitry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-clang-1.diff
Type: application/octet-stream
Size: 447 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/89190fcc/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-compiler-rt-1.diff
Type: application/octet-stream
Size: 890 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/89190fcc/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-mlir-1.diff
Type: application/octet-stream
Size: 545 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/89190fcc/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-test-suite-1.diff
Type: application/octet-stream
Size: 552 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/89190fcc/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/89190fcc/attachment.sig>

Andrew Kelley via llvm-dev

2020-Feb-06 14:38 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

I filed https://bugs.llvm.org/show_bug.cgi?id=44780 but was able to work
around it with
https://github.com/ziglang/zig/commit/73256dda91d0d5b3d13016d15f2c4465a69cd7d4.

Other than that, all tests passing in zig's llvm10 branch, with
assertions-enabled debug-mode LLVM. I tested with release/10.x branch,
commit 2d9954dd8244c7a9d6a1e160fcbb22fe2b9b514f.

Good luck with the release,
Andrew

On 1/30/20 2:38 PM, Hans Wennborg via llvm-dev wrote:> Hello everyone,
> 
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
> 
> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
> 
> Pre-built binaries will be added there as they become available.
> 
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
> 
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
> 
> Release Candidate 2 was previously scheduled for February 2. Because
> of the late RC1, I've pushed this back a bit to the 11th.
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/313c2b08/attachment.sig>

Rainer Orth via llvm-dev

2020-Feb-06 15:08 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Hi Hans,
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
>
> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
>
> Pre-built binaries will be added there as they become available.
I've already uploaded Solaris 11.4/AMD64 and Solaris 11.4/SPARCv9
binaries to releases-origin.llvm.org some time ago.

While amd64-pc-solaris2.11 results are en par with the LLVM 9.0.0 ones
(some failures fixed or xfailed since then)

  Expected Passes    : 54488
  Expected Failures  : 180
  Unsupported Tests  : 2409
  Unexpected Failures: 23

the sparcv9-sun-solaris2.11 ones are horrible compared to the 9.0.0 ones:

* 9.0.0 final:

  Expected Passes    : 48477
  Expected Failures  : 180
  Unsupported Tests  : 1443
  Unexpected Passes  : 1
  Unexpected Failures: 382

* 10.0.0 rc1:

  Expected Passes    : 47959
  Expected Failures  : 186
  Unsupported Tests  : 1615
  Unexpected Passes  : 1
  Unexpected Failures: 4278

A large number of those only occur for non-SPARC targets (something I
usually don't test at all), and even the buildbot is way way better with
only 51 unexpected failures.  However, that one only does a 1-stage
build where errors due to Bug 42535 don't occur.  Still, comparing
master results on Solaris 11.5/SPARC for all targets between a 1-stage
build with gcc 9.1.0 and a 2-stage build shows a similar pattern:

* 1-stage:

  Expected Passes    : 53734
  Expected Failures  : 205
  Unsupported Tests  : 2495
  Unexpected Passes  : 1
  Unexpected Failures: 228

* 2-stage:

  Expected Passes    : 45756
  Expected Failures  : 205
  Unsupported Tests  : 2495
  Unexpected Passes  : 2
  Unexpected Failures: 7303

I fear this is effectively impossible to analyze let alone fix for the
10.0.0 release.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

Anil Mahmud via llvm-dev

2020-Feb-06 21:03 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Hello I finished testing RC 10.0.0 on Power PC 64bit Little Endian Red Hat
7.4 machine and have uploaded the binary.

The only failure I detected was when running test-release.sh :
> FAIL: LLVM :: tools/llvm-ar/quick-append.test (53100 of 59657)
> ******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test'FAILED ********************

^
> This was fixed in f00ab188f4e4214dfbecfdd8968a183e9363cefa on master
> and cherry-picked to 10.x as e11d70cfe7e2a8537eb774ed1780e9ecd1aa90a0.
The sha1 file is attached.

Thanks,
Anil Mahmud.

On Thu, Feb 6, 2020 at 11:24 AM Rainer Orth via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi Hans,
>
> > It took a bit longer than planned due to master being a somewhat
> > unstable at the branch point, but Release Candidate 1 has now been
> > tagged as llvmorg-10.0.0-rc1.
> >
> > Source code and docs are available at
> https://prereleases.llvm.org/10.0.0/#rc1
> >
> > Pre-built binaries will be added there as they become available.
>
> I've already uploaded Solaris 11.4/AMD64 and Solaris 11.4/SPARCv9
> binaries to releases-origin.llvm.org some time ago.
>
> While amd64-pc-solaris2.11 results are en par with the LLVM 9.0.0 ones
> (some failures fixed or xfailed since then)
>
>   Expected Passes    : 54488
>   Expected Failures  : 180
>   Unsupported Tests  : 2409
>   Unexpected Failures: 23
>
> the sparcv9-sun-solaris2.11 ones are horrible compared to the 9.0.0 ones:
>
> * 9.0.0 final:
>
>   Expected Passes    : 48477
>   Expected Failures  : 180
>   Unsupported Tests  : 1443
>   Unexpected Passes  : 1
>   Unexpected Failures: 382
>
> * 10.0.0 rc1:
>
>   Expected Passes    : 47959
>   Expected Failures  : 186
>   Unsupported Tests  : 1615
>   Unexpected Passes  : 1
>   Unexpected Failures: 4278
>
> A large number of those only occur for non-SPARC targets (something I
> usually don't test at all), and even the buildbot is way way better
with
> only 51 unexpected failures.  However, that one only does a 1-stage
> build where errors due to Bug 42535 don't occur.  Still, comparing
> master results on Solaris 11.5/SPARC for all targets between a 1-stage
> build with gcc 9.1.0 and a 2-stage build shows a similar pattern:
>
> * 1-stage:
>
>   Expected Passes    : 53734
>   Expected Failures  : 205
>   Unsupported Tests  : 2495
>   Unexpected Passes  : 1
>   Unexpected Failures: 228
>
> * 2-stage:
>
>   Expected Passes    : 45756
>   Expected Failures  : 205
>   Unsupported Tests  : 2495
>   Unexpected Passes  : 2
>   Unexpected Failures: 7303
>
> I fear this is effectively impossible to analyze let alone fix for the
> 10.0.0 release.
>
>         Rainer
>
> --
>
>
-----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/8cb6907a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clang+llvm-10.0.0-rc1-powerpc64le-linux-rhel-7.4.sha1
Type: application/octet-stream
Size: 98 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/8cb6907a/attachment.obj>

Neil Nelson via llvm-dev

2020-Feb-07 04:38 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Uploaded for Xubuntu/Ubuntu 19.10.

sha256sum clang+llvm-10.0.0-rc1-x86_64-pc-linux-gnu.tar.xz
829c1f5a090666d2971b5f58fa34d24b5067a7969178bfc122a9b2df77432843

Is ParallelSTL something that should be installed? If so it is not clear 
at the ParallelSTL GitHub site and related pages how that should be done.

In logs directory.
grep fail *.log | sort | uniq

deferred_errors.log:[Release+Asserts Phase3] check-all failed
deferred_errors.log:[Release+Asserts Phase3] test suite failed
deferred_errors.log:[Release Phase3] check-all failed
deferred_errors.log:[Release Phase3] test suite failed
llvm.check-Phase3-Release+Asserts.log:clang-10: clang-10: errorerror: : 
clang frontend command failed due to signal (use -v to see 
invocation)clang frontend command failed due to signal (use -v to see 
invocation)
llvm.check-Phase3-Release+Asserts.log:clang-10: error: clang frontend 
command failed due to signal (use -v to see invocation)
llvm.check-Phase3-Release+Asserts.log:clang-10: error: clang frontend 
command failed due to signal (use -v to see invocation)
llvm.check-Phase3-Release+Asserts.log:: clang frontend command failed 
due to signal (use -v to see invocation)
llvm.check-Phase3-Release+Asserts.log:clang frontend command failed due 
to signal (use -v to see invocation)
llvm.check-Phase3-Release+Asserts.log:clang frontend command failed due 
to signal (use -v to see invocation)InstalledDir: 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin
llvm.check-Phase3-Release+Asserts.log:error#28:  clang frontend command 
failed due to signal (use -v to see invocation)0x000000000248cb2e
llvm.check-Phase3-Release+Asserts.log::  error#7:  clang frontend 
command failed due to signal (use -v to see invocation)0x00007fa6cc086899
llvm.check-Phase3-Release.log:clang-10: error: clang frontend command 
failed due to signal (use -v to see invocation)
llvm.configure-Phase1-Release+Asserts.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.configure-Phase1-Release.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.configure-Phase2-Release+Asserts.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.configure-Phase2-Release.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.configure-Phase3-Release+Asserts.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.configure-Phase3-Release.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.make-Phase1-Release+Asserts.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.make-Phase1-Release.log:-- Could not find ParallelSTL, libc++abi 
will not attempt to use it but the build may fail if the libc++ in use 
needs it to be available.
llvm.make-Phase2-Release+Asserts.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.make-Phase2-Release.log:-- Could not find ParallelSTL, libc++abi 
will not attempt to use it but the build may fail if the libc++ in use 
needs it to be available.
llvm.make-Phase3-Release+Asserts.log:-- Could not find ParallelSTL, 
libc++abi will not attempt to use it but the build may fail if the 
libc++ in use needs it to be available.
llvm.make-Phase3-Release.log:-- Could not find ParallelSTL, libc++abi 
will not attempt to use it but the build may fail if the libc++ in use 
needs it to be available.
testing.10.0.0-rc1.log:clang-10: clang-10: errorerror: : clang frontend 
command failed due to signal (use -v to see invocation)clang frontend 
command failed due to signal (use -v to see invocation)
testing.10.0.0-rc1.log:clang-10: error: clang frontend command failed 
due to signal (use -v to see invocation)
testing.10.0.0-rc1.log:clang-10: error: clang frontend command failed 
due to signal (use -v to see invocation)
testing.10.0.0-rc1.log:: clang frontend command failed due to signal 
(use -v to see invocation)
testing.10.0.0-rc1.log:clang frontend command failed due to signal (use 
-v to see invocation)
testing.10.0.0-rc1.log:clang frontend command failed due to signal (use 
-v to see invocation)InstalledDir: 
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin
testing.10.0.0-rc1.log:-- Could not find ParallelSTL, libc++abi will not 
attempt to use it but the build may fail if the libc++ in use needs it 
to be available.
testing.10.0.0-rc1.log:error#28:  clang frontend command failed due to 
signal (use -v to see invocation)0x000000000248cb2e
testing.10.0.0-rc1.log::  error#7:  clang frontend command failed due to 
signal (use -v to see invocation)0x00007fa6cc086899
testing.10.0.0-rc1.log:-- Performing Test HAVE_GNU_POSIX_REGEX -- failed 
to compile
testing.10.0.0-rc1.log:-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES 
-- failed to compile
testing.10.0.0-rc1.log:[Release+Asserts Phase3] check-all failed
testing.10.0.0-rc1.log:[Release+Asserts Phase3] test suite failed
testing.10.0.0-rc1.log:[Release Phase3] check-all failed
testing.10.0.0-rc1.log:[Release Phase3] test suite failed

 From testing.10.0.0-rc1.log
testing.10.0.0-rc1.log:FAIL: LLVM :: tools/llvm-ar/quick-append.test 
(53138 of 69456)
testing.10.0.0-rc1.log:******************** TEST 'LLVM :: 
tools/llvm-ar/quick-append.test' FAILED ********************
testing.10.0.0-rc1.log:FAIL: LLVM :: tools/llvm-ar/quick-append.test 
(53160 of 69493)
testing.10.0.0-rc1.log:******************** TEST 'LLVM :: 
tools/llvm-ar/quick-append.test' FAILED ********************


# SAME-NEXT: 1.o
              ^
<stdin>:1:156: note: 'next' match was here
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release+Asserts/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
^
<stdin>:1:105: note: previous match ended here
/home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release+Asserts/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
^

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..

15 warning(s) in tests

Testing Time: 696.88s
********************
Failing Tests (1):
     LLVM :: tools/llvm-ar/quick-append.test

   Expected Passes    : 67312
   Expected Failures  : 272
   Unsupported Tests  : 1908
   Unexpected Failures: 1
make[3]: *** [CMakeFiles/check-all.dir/build.make:58: 
CMakeFiles/check-all] Error 1
make[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of 
errors.
make[2]: *** [CMakeFiles/Makefile2:358: CMakeFiles/check-all.dir/all] 
Error 2
make[1]: *** [CMakeFiles/Makefile2:365: CMakeFiles/check-all.dir/rule] 
Error 2
make[1]: Target 'check-all' not remade because of errors.
make: *** [Makefile:238: check-all] Error 2
[Release+Asserts Phase3] check-all failed

Neil Nelson

On 1/30/20 12:38 PM, Hans Wennborg via llvm-dev wrote:> Hello everyone,
>
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
>
> Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
>
> Pre-built binaries will be added there as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> Release Candidate 2 was previously scheduled for February 2. Because
> of the late RC1, I've pushed this back a bit to the 11th.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/b075eb66/attachment-0001.html>

Hans Wennborg via llvm-dev

2020-Feb-10 12:16 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Great, thanks for testing!

On Thu, Feb 6, 2020 at 3:38 PM Andrew Kelley via llvm-dev
<llvm-dev at lists.llvm.org> wrote:>
> I filed https://bugs.llvm.org/show_bug.cgi?id=44780 but was able to work
> around it with
>
https://github.com/ziglang/zig/commit/73256dda91d0d5b3d13016d15f2c4465a69cd7d4.
>
> Other than that, all tests passing in zig's llvm10 branch, with
> assertions-enabled debug-mode LLVM. I tested with release/10.x branch,
> commit 2d9954dd8244c7a9d6a1e160fcbb22fe2b9b514f.
>
> Good luck with the release,
> Andrew
>
> On 1/30/20 2:38 PM, Hans Wennborg via llvm-dev wrote:
> > Hello everyone,
> >
> > It took a bit longer than planned due to master being a somewhat
> > unstable at the branch point, but Release Candidate 1 has now been
> > tagged as llvmorg-10.0.0-rc1.
> >
> > Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
> >
> > Pre-built binaries will be added there as they become available.
> >
> > Please file bug reports for any issues you find as blockers of
> > https://llvm.org/pr44555
> >
> > Release testers: please start your engines, run the script, share your
> > results, and upload binaries.
> >
> > Release Candidate 2 was previously scheduled for February 2. Because
> > of the late RC1, I've pushed this back a bit to the 11th.
> >
> > Thanks,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Hans Wennborg via llvm-dev

2020-Feb-10 15:25 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

On Thu, Feb 6, 2020 at 5:24 PM Rainer Orth via llvm-dev
<llvm-dev at lists.llvm.org> wrote:>
> Hi Hans,
>
> > It took a bit longer than planned due to master being a somewhat
> > unstable at the branch point, but Release Candidate 1 has now been
> > tagged as llvmorg-10.0.0-rc1.
> >
> > Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc1
> >
> > Pre-built binaries will be added there as they become available.
>
> I've already uploaded Solaris 11.4/AMD64 and Solaris 11.4/SPARCv9
> binaries to releases-origin.llvm.org some time ago.
Sorry, I missed this. Did you send an email when you uploaded? Can you
please share the SHA1 or similar hashes so I can verify that I get the
right ones on my end?
> While amd64-pc-solaris2.11 results are en par with the LLVM 9.0.0 ones
> (some failures fixed or xfailed since then)
>
>   Expected Passes    : 54488
>   Expected Failures  : 180
>   Unsupported Tests  : 2409
>   Unexpected Failures: 23
>
> the sparcv9-sun-solaris2.11 ones are horrible compared to the 9.0.0 ones:
>
> * 9.0.0 final:
>
>   Expected Passes    : 48477
>   Expected Failures  : 180
>   Unsupported Tests  : 1443
>   Unexpected Passes  : 1
>   Unexpected Failures: 382
>
> * 10.0.0 rc1:
>
>   Expected Passes    : 47959
>   Expected Failures  : 186
>   Unsupported Tests  : 1615
>   Unexpected Passes  : 1
>   Unexpected Failures: 4278
>
> A large number of those only occur for non-SPARC targets (something I
> usually don't test at all), and even the buildbot is way way better
with
> only 51 unexpected failures.  However, that one only does a 1-stage
> build where errors due to Bug 42535 don't occur.  Still, comparing
> master results on Solaris 11.5/SPARC for all targets between a 1-stage
> build with gcc 9.1.0 and a 2-stage build shows a similar pattern:
>
> * 1-stage:
>
>   Expected Passes    : 53734
>   Expected Failures  : 205
>   Unsupported Tests  : 2495
>   Unexpected Passes  : 1
>   Unexpected Failures: 228
>
> * 2-stage:
>
>   Expected Passes    : 45756
>   Expected Failures  : 205
>   Unsupported Tests  : 2495
>   Unexpected Passes  : 2
>   Unexpected Failures: 7303
>
> I fear this is effectively impossible to analyze let alone fix for the
> 10.0.0 release.
Thanks for the report!

I guess since this doesn't seem to be well covered by continuous
testing, it's not going to be good :-/

Should we highlight the status of Solaris/Sparc support in the release
notes somehow?

Thanks,
Hans

Hans Wennborg via llvm-dev

2020-Feb-10 15:43 UTC

head link

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

On Fri, Feb 7, 2020 at 5:39 AM Neil Nelson via llvm-dev
<llvm-dev at lists.llvm.org> wrote:>
> Uploaded for Xubuntu/Ubuntu 19.10.
>
> sha256sum clang+llvm-10.0.0-rc1-x86_64-pc-linux-gnu.tar.xz
> 829c1f5a090666d2971b5f58fa34d24b5067a7969178bfc122a9b2df77432843
This! I've added it to the pre-release.
>
> Is ParallelSTL something that should be installed? If so it is not clear at
the ParallelSTL GitHub site and related pages how that should be done.
I don't think it is.. are you sure the ParallelSTL mentions in the log
are not just benign messages from cmake?
> From testing.10.0.0-rc1.log
> testing.10.0.0-rc1.log:FAIL: LLVM :: tools/llvm-ar/quick-append.test (53138
of 69456)
> testing.10.0.0-rc1.log:******************** TEST 'LLVM ::
tools/llvm-ar/quick-append.test' FAILED ********************
> testing.10.0.0-rc1.log:FAIL: LLVM :: tools/llvm-ar/quick-append.test (53160
of 69493)
> testing.10.0.0-rc1.log:******************** TEST 'LLVM ::
tools/llvm-ar/quick-append.test' FAILED ********************
This one has been fixed, so should be good in rc2.

Thanks,
Hans

Seemingly Similar Threads

Search for more possibly parallel threads

llvm dev - Feb 2020 - [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

[llvm-dev] [10.0.0 Release] Release Candidate 1 is here

Seemingly Similar Threads