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

Sylvestre Ledru via llvm-dev llvm-dev at lists.llvm.org
Mon Mar 23 08:25:59 PDT 2020


Le 23/03/2020 à 15:49, Hans Wennborg a écrit :
> On Sun, Mar 22, 2020 at 9:05 PM Andrew Kelley <andrew at ziglang.org> wrote:
>>
>> 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.
> 
> That sounds reasonable to me. +Sylvestre Ledru  do you control these
> package configs?
> 

I do but I don't think disabling polly is the right option (and I have seen
people using polly from the package).
Instead, we should fix the issue (maybe only in the Debian/Ubuntu package).

Cheers,
Sylvestre


More information about the llvm-dev mailing list