compiler-explorer: [BUG]: Clang trunk builds haven't updated since May 8

Describe the bug

The build of clang trunk appears to have stopped being updated after 9a12138b5fd8c807c3b95144236c07dfc323974f.

Steps to reproduce

Full compiler version
clang version 15.0.0 (https://github.com/llvm/llvm-project.git 9a12138b5fd8c807c3b95144236c07dfc323974f)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/compiler-explorer/clang-assertions-trunk/bin

Expected behavior

Usually the compiler explorer builds are only about 24 hours behind trunk.

Reproduction link

Not applicable

Screenshots

Not applicable

Operating System

No response

Browser version

No response

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (15 by maintainers)

Most upvoted comments

https://github.com/compiler-explorer/compiler-workflows/actions/runs/2332985777 - fingers crossed 😃 (am at DayJob ™️ right now hence spotty replies, will hopefully get this deployed soon though)

mattgodbolt on May 16, 2022

A post-review comment on https://reviews.llvm.org/D125315 is currently discussing this:

The OpenMP offloading runtime was always intended to be built with a newly-built Clang, either through a two-phase build or with -DLLVM_ENABLE_RUNTIMES=openmp. This patch added some code that uses standard CMake to build the library, rather than locating the clang binary directly. I could add some code to skip building this static library, or the device runtime entirely, if the compiler isn’t an up-to-date Clang. I’m not sure what the best solution to this is, since we always required that this was to be built with Clang, this patch just made it a more strict requirement.

RKSimon on May 16, 2022

Actually, or maybe it’s expecting to be built with Clang? It’s passing -mllvm, that can’t be a gcc argument, can it?

partouf on May 16, 2022