Hi,
we've updated OpenMandriva, and started a mass build. Looks good so far, except we found 1 more bug (not a regression from previous RCs, but newly exposed by a package update introducing code that triggers it).
I don't think this is an extremely serious bug (takes a few not too common constructs to trigger it), but still would be nice to fix given a lot of users will likely run into it (we can't be the only distro that ships libtorrent-rasterbar).
Probably not worth making it a blocker, but we've run into this while rebuilding our "unsupported" repo (which is basically a collection of old junk that may still be used by a few people, but that nobody is committing to maintain anymore):
I realize it's late but I've just gotten a major bug report. Long story
short, if you happen to have CUDA toolkit 10.2 installed, clang throws
warnings on every compilation (even non-CUDA) which in turns breaks
CMake checks, which in turn means you can't compile pretty much anything
correctly (including LLVM itself).
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 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.
I don’t know if you’ll be planning on RC6, but this bug: https://bugs.llvm.org/show_bug.cgi?id=45271 was just filed as a regression in LLVM 10 versus LLVM 9, and looks like it could break things (potentially silently) for at least some installations of llvm-strip. There’s a fix that’s basically ready (https://reviews.llvm.org/D76562). I’ll leave it up to you as to whether the fix should be included in the release or not (it almost certainly should be in a patch release if it doesn’t, I think).
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).