[10.0.0 Release] Release Candidate 1 is here

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

[10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
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
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <[hidden email]> 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


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

fix-clang-1.diff (461 bytes) Download Attachment
fix-compiler-rt-1.diff (906 bytes) Download Attachment
fix-test-suite-1.diff (573 bytes) Download Attachment
signature.asc (230 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
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


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (631 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On Fri, Jan 31, 2020 at 9:37 PM Dimitry Andric <[hidden email]> wrote:

>
> On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <[hidden email]> 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
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On Fri, Jan 31, 2020 at 9:51 PM Michał Górny <[hidden email]> 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!
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On Thu, 2020-01-30 at 14:38 -0500, Hans Wennborg via cfe-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
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

I didn't open any bugs yet, because as of yet I'm not sure the problem
isn't on my side.

I checked out the release branch (release/10.x) and configured to build
clang with compiler-rt enabled:

cmake -B build -S llvm -DCMAKE_BUILD_TYPE=Release
-DCMAKE_INSTALL_PREFIX=/usr/lib/llvm-10
-DLLVM_ENABLE_PROJECTS='clang;libcxx;libcxxabi;compiler-rt'

When I then build the program, it results in a linker error:

[ 79%] Linking CXX shared library
../../../../lib/clang/10.0.0/lib/linux/libclang_rt.hwasan-x86_64.so
/usr/bin/ld: CMakeFiles/RTHwasan_dynamic.x86_64.dir/hwasan.cpp.o:
relocation R_X86_64_PC32 against undefined symbol `__ehdr_start' can
not be used when making a shared object; recompile with -fPIC

Looking at the offending code, it mentions that it is supposed to be a
"statically linked executable":

  // In the non-static code path we call dl_iterate_phdr here. But at
this point
  // libc might not have been initialized enough for dl_iterate_phdr to
work.
  // Fortunately, since this is a statically linked executable we can
use the
  // linker-defined symbol __ehdr_start to find the only relevant set
of phdrs.
  extern ElfW(Ehdr) __ehdr_start;

Clearly, some of these assumptions aren't holding true and it's trying
to use this inside a shared object.

If I build clang without compiler-rt I do not get any linker errors and
the compiler works as expected. Is this a new bug or am I doing
something wrong?


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
On Mon, Feb 3, 2020 at 11:17 AM Martijn Otto via cfe-dev
<[hidden email]> wrote:

> I didn't open any bugs yet, because as of yet I'm not sure the problem
> isn't on my side.
>
> I checked out the release branch (release/10.x) and configured to build
> clang with compiler-rt enabled:
>
> cmake -B build -S llvm -DCMAKE_BUILD_TYPE=Release
> -DCMAKE_INSTALL_PREFIX=/usr/lib/llvm-10
> -DLLVM_ENABLE_PROJECTS='clang;libcxx;libcxxabi;compiler-rt'
>
> When I then build the program, it results in a linker error:
>
> [ 79%] Linking CXX shared library
> ../../../../lib/clang/10.0.0/lib/linux/libclang_rt.hwasan-x86_64.so
> /usr/bin/ld: CMakeFiles/RTHwasan_dynamic.x86_64.dir/hwasan.cpp.o:
> relocation R_X86_64_PC32 against undefined symbol `__ehdr_start' can
> not be used when making a shared object; recompile with -fPIC
[..]
> If I build clang without compiler-rt I do not get any linker errors and
> the compiler works as expected. Is this a new bug or am I doing
> something wrong?

This sounds like https://bugs.llvm.org/show_bug.cgi?id=42994
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On 3 Feb 2020, at 10:57, Hans Wennborg <[hidden email]> wrote:
>
> On Fri, Jan 31, 2020 at 9:37 PM Dimitry Andric <[hidden email]> wrote:
...

>> 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?
Filed <https://bugs.llvm.org/show_bug.cgi?id=44763>.  I didn't have a
debug build of clang, so not a really informative backtrace yet.

I suppose the pre-supplied .bc files don't really get processed well by
recent versions of clang.  I hope that others can reproduce this.

-Dimitry


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (230 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <[hidden email]> 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


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (230 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
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 <[hidden email]>
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 <[hidden email]> wrote:
On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <[hidden email]> 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
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
The following error was found when running test-release.sh on Red Hat 7.4

********************
FAIL: LLVM :: tools/llvm-ar/quick-append.test (53100 of 59657)
******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' FAILED ********************
Script:
--
: 'RUN: at line 3';   rm -rf /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp && mkdir -p /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp
: 'RUN: at line 4';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/yaml2obj /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test -o /scratch/anil/llvm1000_rc1_binary_upload/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';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/yaml2obj /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test -o /scratch/anil/llvm1000_rc1_binary_upload/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';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 9';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SINGLE --match-full-lines --implicit-check-not {{.}}
: 'RUN: at line 14';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SINGLE-SYM
: 'RUN: at line 20';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
: 'RUN: at line 21';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MULTIPLE --match-full-lines --implicit-check-not {{.}}
: 'RUN: at line 27';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MULTIPLE-SYM
: 'RUN: at line 34';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 35';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SAME -DFILE=/scratch/anil/llvm1000_rc1_binary_upload/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';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SAME-SYM
: 'RUN: at line 48';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
: 'RUN: at line 49';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/count 0
: 'RUN: at line 51';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/count 0
: 'RUN: at line 54';   not /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc 2>&1    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=NO-ARCHIVE
: 'RUN: at line 60';   not /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.txt 2>&1    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MISSING-FILE -DFILE=/scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.txt
: 'RUN: at line 66';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qcT /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 67';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qcT /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
: 'RUN: at line 68';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MULTIPLE
: 'RUN: at line 71';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qcT /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-same.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
: 'RUN: at line 72';   /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-same.a    | /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SAME
--
Exit Code: 1

Command Output (stderr):
--
+ : 'RUN: at line 3'
+ rm -rf /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp
+ mkdir -p /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp
+ : 'RUN: at line 4'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/yaml2obj /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test -o /scratch/anil/llvm1000_rc1_binary_upload/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'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/yaml2obj /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test -o /scratch/anil/llvm1000_rc1_binary_upload/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'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
+ : 'RUN: at line 9'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SINGLE --match-full-lines --implicit-check-not '{{.}}'
+ : 'RUN: at line 14'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/single.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SINGLE-SYM
+ : 'RUN: at line 20'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
+ : 'RUN: at line 21'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MULTIPLE --match-full-lines --implicit-check-not '{{.}}'
+ : 'RUN: at line 27'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/multiple.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MULTIPLE-SYM
+ : 'RUN: at line 34'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
+ : 'RUN: at line 35'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SAME -DFILE=/scratch/anil/llvm1000_rc1_binary_upload/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'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/same.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SAME-SYM
+ : 'RUN: at line 48'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
+ : 'RUN: at line 49'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/count 0
+ : 'RUN: at line 51'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-nm --print-armap /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/without.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/count 0
+ : 'RUN: at line 54'
+ not /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=NO-ARCHIVE
+ : 'RUN: at line 60'
+ not /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qc /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.txt
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MISSING-FILE -DFILE=/scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/missing.txt
+ : 'RUN: at line 66'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qcT /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
+ : 'RUN: at line 67'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qcT /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/2.o
+ : 'RUN: at line 68'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-multiple.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=MULTIPLE
+ : 'RUN: at line 71'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar qcT /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-same.a /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
+ : 'RUN: at line 72'
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/llvm-ar t /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/thin-same.a
+ /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/bin/FileCheck /scratch/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/llvm/test/tools/llvm-ar/quick-append.test --check-prefix=SAME
/scratch/anil/llvm1000_rc1_binary_upload/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:133: note: 'next' match was here
/scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
                                                                                                                                    ^
<stdin>:1:82: note: previous match ended here
/scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
                                                                                 ^

--

On Wed, Feb 5, 2020 at 3:00 PM Anil Mahmud <[hidden email]> wrote:
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 <[hidden email]>
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 <[hidden email]> wrote:
On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <[hidden email]> 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
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On 4 Feb 2020, at 12:06, Dimitry Andric via Release-testers <[hidden email]> wrote:
>
> On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers <[hidden email]> 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

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

fix-clang-1.diff (461 bytes) Download Attachment
fix-compiler-rt-1.diff (906 bytes) Download Attachment
fix-mlir-1.diff (556 bytes) Download Attachment
fix-test-suite-1.diff (573 bytes) Download Attachment
signature.asc (230 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On Wed, Feb 5, 2020 at 9:00 PM Anil Mahmud <[hidden email]> wrote:

>
> 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
[..]
> Can this be backported to RC1 10.0.0 ?

Yes, thanks for finding it! Cherry-picked to the 10.x branch as
cbec01fe05895abe96f2cb80e24367dec60209ee (We can't backport it to RC1
since that's already been released, but this will be part of RC2.)

Thanks,
Hans
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On Wed, Feb 5, 2020 at 9:30 PM Anil Mahmud <[hidden email]> wrote:
>
> The following error was found when running test-release.sh on Red Hat 7.4
>
> ********************
> FAIL: LLVM :: tools/llvm-ar/quick-append.test (53100 of 59657)
> ******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' FAILED ********************

[...]

> /scratch/anil/llvm1000_rc1_binary_upload/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:133: note: 'next' match was here
> /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
>                                                                                                                                     ^
> <stdin>:1:82: note: previous match ended here
> /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
>                                                                                  ^

This was fixed in f00ab188f4e4214dfbecfdd8968a183e9363cefa on master
and cherry-picked to 10.x as e11d70cfe7e2a8537eb774ed1780e9ecd1aa90a0.

Thanks,
Hans
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
Hi,

here are the results for ARM targets:

* 32-bit has the same issue reported in PR44767

* same issue with quick-append.text for AArch64 check-all results are:
Testing Time: 4520.30s
********************
Failing Tests (1):
    LLVM :: tools/llvm-ar/quick-append.test

  Expected Passes    : 65318
  Expected Failures  : 256
  Unsupported Tests  : 3384
  Unexpected Failures: 1

And a bunch of errors in the testsuite:

FAILED: Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/test-suite-build/tools/timeit
--summary Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o.time
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin/clang++
 -DNDEBUG  -O3 -DNDEBUG   -w -Werror=date-time -MD -MT
Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
-MF Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o.d
-o Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
-c /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm-test-suite/Bitcode/simd_ops/AArch64_halide_runtime.bc
double free or corruption (fasttop)
Stack dump:
0. Program arguments:
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin/clang++
-DNDEBUG -O3 -DNDEBUG -w -Werror=date-time -MD -MT
Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
-MF Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o.d
-o Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
-c /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm-test-suite/Bitcode/simd_ops/AArch64_halide_runtime.bc
1. Per-module optimization passes
2. Running pass 'Global Variable Optimizer' on module
'/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm-test-suite/Bitcode/simd_ops/AArch64_halide_runtime.bc'.
malloc_consolidate(): invalid chunk size
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/test-suite-build/tools/timeit:
error: child terminated by signal 6


Binaires uploaded:
469408981edd3c2be8e8ee6e86199abb6f3faa65e8cb66d194050975472ee359
clang+llvm-10.0.0-rc1-aarch64-linux-gnu.tar.xz

Thanks,
Yvan

On Thu, 6 Feb 2020 at 10:30, Hans Wennborg via cfe-dev
<[hidden email]> wrote:

>
> On Wed, Feb 5, 2020 at 9:30 PM Anil Mahmud <[hidden email]> wrote:
> >
> > The following error was found when running test-release.sh on Red Hat 7.4
> >
> > ********************
> > FAIL: LLVM :: tools/llvm-ar/quick-append.test (53100 of 59657)
> > ******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' FAILED ********************
>
> [...]
>
> > /scratch/anil/llvm1000_rc1_binary_upload/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:133: note: 'next' match was here
> > /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
> >                                                                                                                                     ^
> > <stdin>:1:82: note: previous match ended here
> > /scratch/anil/llvm1000_rc1_binary_upload/rc1/Phase3/Release/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o
> >                                                                                  ^
>
> This was fixed in f00ab188f4e4214dfbecfdd8968a183e9363cefa on master
> and cherry-picked to 10.x as e11d70cfe7e2a8537eb774ed1780e9ecd1aa90a0.
>
> Thanks,
> Hans
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
On 6 Feb 2020, at 11:16, Yvan Roux via Release-testers <[hidden email]> wrote:
...

> And a bunch of errors in the testsuite:
>
> FAILED: Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
> /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/test-suite-build/tools/timeit
> --summary Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o.time
> /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin/clang++
> -DNDEBUG  -O3 -DNDEBUG   -w -Werror=date-time -MD -MT
> Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
> -MF Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o.d
> -o Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
> -c /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm-test-suite/Bitcode/simd_ops/AArch64_halide_runtime.bc
> double free or corruption (fasttop)
> Stack dump:
> 0. Program arguments:
> /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin/clang++
> -DNDEBUG -O3 -DNDEBUG -w -Werror=date-time -MD -MT
> Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
> -MF Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o.d
> -o Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o
> -c /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm-test-suite/Bitcode/simd_ops/AArch64_halide_runtime.bc
> 1. Per-module optimization passes
> 2. Running pass 'Global Variable Optimizer' on module
> '/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm-test-suite/Bitcode/simd_ops/AArch64_halide_runtime.bc'.
> malloc_consolidate(): invalid chunk size
> /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/test-suite-build/tools/timeit:
> error: child terminated by signal 6
Yes, this looks almost certainly like https://bugs.llvm.org/show_bug.cgi?id=44763.

From the last lines of your output, I assume it is some sort of double
free issue.  Might be worth running it under valgrind, or with ASan
enabled?

-Dimitry


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (230 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
In reply to this post by Hans Wennborg via cfe-dev
On Thu, Feb 6, 2020 at 11:16 AM Yvan Roux <[hidden email]> wrote:

>
> Hi,
>
> here are the results for ARM targets:
>
> * 32-bit has the same issue reported in PR44767
>
> * same issue with quick-append.text for AArch64 check-all results are:
> Testing Time: 4520.30s
> ********************
> Failing Tests (1):
>     LLVM :: tools/llvm-ar/quick-append.test
>
>   Expected Passes    : 65318
>   Expected Failures  : 256
>   Unsupported Tests  : 3384
>   Unexpected Failures: 1
>
> And a bunch of errors in the testsuite:

[..]

> Binaires uploaded:
> 469408981edd3c2be8e8ee6e86199abb6f3faa65e8cb66d194050975472ee359
> clang+llvm-10.0.0-rc1-aarch64-linux-gnu.tar.xz

It looks like the binary wasn't fully uploaded. It's only 48 MB and
the hash doesn't match. Can you try uploading it again?
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
Hi Hans,

On Thu, 6 Feb 2020 at 12:40, Hans Wennborg <[hidden email]> wrote:

>
> On Thu, Feb 6, 2020 at 11:16 AM Yvan Roux <[hidden email]> wrote:
> >
> > Hi,
> >
> > here are the results for ARM targets:
> >
> > * 32-bit has the same issue reported in PR44767
> >
> > * same issue with quick-append.text for AArch64 check-all results are:
> > Testing Time: 4520.30s
> > ********************
> > Failing Tests (1):
> >     LLVM :: tools/llvm-ar/quick-append.test
> >
> >   Expected Passes    : 65318
> >   Expected Failures  : 256
> >   Unsupported Tests  : 3384
> >   Unexpected Failures: 1
> >
> > And a bunch of errors in the testsuite:
>
> [..]
>
> > Binaires uploaded:
> > 469408981edd3c2be8e8ee6e86199abb6f3faa65e8cb66d194050975472ee359
> > clang+llvm-10.0.0-rc1-aarch64-linux-gnu.tar.xz
>
> It looks like the binary wasn't fully uploaded. It's only 48 MB and
> the hash doesn't match. Can you try uploading it again?

Sorry, office network is pretty bad today! the upload seems to be
completed now, is the sha256sum right this time ?
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] [10.0.0 Release] Release Candidate 1 is here

Hans Wennborg via cfe-dev
On Thu, Feb 6, 2020 at 1:14 PM Yvan Roux <[hidden email]> wrote:

>
> Hi Hans,
>
> On Thu, 6 Feb 2020 at 12:40, Hans Wennborg <[hidden email]> wrote:
> >
> > On Thu, Feb 6, 2020 at 11:16 AM Yvan Roux <[hidden email]> wrote:
> > >
> > > Hi,
> > >
> > > here are the results for ARM targets:
> > >
> > > * 32-bit has the same issue reported in PR44767
> > >
> > > * same issue with quick-append.text for AArch64 check-all results are:
> > > Testing Time: 4520.30s
> > > ********************
> > > Failing Tests (1):
> > >     LLVM :: tools/llvm-ar/quick-append.test
> > >
> > >   Expected Passes    : 65318
> > >   Expected Failures  : 256
> > >   Unsupported Tests  : 3384
> > >   Unexpected Failures: 1
> > >
> > > And a bunch of errors in the testsuite:
> >
> > [..]
> >
> > > Binaires uploaded:
> > > 469408981edd3c2be8e8ee6e86199abb6f3faa65e8cb66d194050975472ee359
> > > clang+llvm-10.0.0-rc1-aarch64-linux-gnu.tar.xz
> >
> > It looks like the binary wasn't fully uploaded. It's only 48 MB and
> > the hash doesn't match. Can you try uploading it again?
>
> Sorry, office network is pretty bad today! the upload seems to be
> completed now, is the sha256sum right this time ?

It looks good now. I've added it to the release. Thanks!
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev