[PATCH] D106781: [Zorg] Use ccache instead incremental build for openmp-offload-cuda-runtime.

[Michael Kruse via Phabricator via llvm-commits]

Meinersbur added a comment.

In D106781#2905360 <https://reviews.llvm.org/D106781#2905360>, @tianshilei1992 wrote:

> Given the fact it's not heavy to build OpenMP, I think a clean build every time should be fine.

ccache hashes the compiler executable. That is, if it turns out to be the same binary, it will re-use the cached result even for the deviceRTL.

> LGTM but better to ask BB owner to take a look.

That would be me.

> Speaking of this, is it possible to integrate the result into Phabricator?

The pre-merge buildkite already uses clean builds with ccache (or sccache). For small changes the incremental build typically is still by some factors faster than the ccache builds which is why I would prefer to keep incremental builds for `openmp-offload-cuda-project`. This also allows us to better identify problems that occur only in one of the builds (such as incorrect builds dependences) and still get frequent rebuilds.

This is a general problem buildbots using LLVM_ENABLE_RUNTIMES builds <https://reviews.llvm.org/rZORG2ed0c6ae25a4da897f23770f9a4976c3e19fff10> and might be fixed some day by e.g. clobbering the runtimes build dir after clang had to be recompiled.


Repository:
  rZORG LLVM Github Zorg

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D106781/new/

https://reviews.llvm.org/D106781