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

[Andrew Kelley via llvm-dev]

On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote:
> Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the
> release branch at 35627038123.
> 
> Source code and docs are available at
> https://prereleases.llvm.org/10.0.0/#rc5 and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5
> 
> If nothing new comes up, I plan to tag 'final' on Monday. Testers, if
> you still have cycles, please take this for a quick spin.

I went ahead and updated all Zig's CI to use rc5, and ran into this problem:

/usr/lib/llvm-10/lib/libclangCodeGen.a(BackendUtil.cpp.o): In function
`(anonymous
namespace)::EmitAssemblyHelper::EmitAssemblyWithNewPassManager(clang::BackendAction,
std::unique_ptr<llvm::raw_pwrite_stream,
std::default_delete<llvm::raw_pwrite_stream> >)':
BackendUtil.cpp:(.text._ZN12_GLOBAL__N_118EmitAssemblyHelper30EmitAssemblyWithNewPassManagerEN5clang13BackendActionESt10unique_ptrIN4llvm17raw_pwrite_streamESt14default_deleteIS5_EE+0x16df):
undefined reference to `getPollyPluginInfo()'
collect2: error: ld returned 1 exit status


This is on Ubuntu Bionic, using apt.llvm.org. I believe this is
https://bugs.llvm.org/show_bug.cgi?id=44870 /
https://github.com/llvm/llvm-project/issues/191

This is a regression from LLVM 9. My suggestion to fix this is, rather
than cutting rc6, to update apt.llvm.org with new binaries, which have
polly disabled. It seems to me that people who want Polly enabled are
compiling from source anyway.

Regards,
Andrew

-------------- 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/20200322/3fe147dd/attachment.sig>