[PATCH] D28492: [buildbot] Add slave to test libomp for ppc64le targets.

[Samuel Antao via Phabricator via llvm-commits]

sfantao added a comment.

Hi Jonas

In https://reviews.llvm.org/D28492#641053, @Hahnfeld wrote:

> Will you (as the bot owner) take care that `/home/bbot/opt/clang` is updated?


The version of clang in /home/bbot/opt/clang is last clang release and it is the stable c/c++ compiler in the machine. I expect to update it when a new release is available.

> Ideally I think libomp should be built together with a full LLVM stack. So, building llvm + clang + openmp for all commits to these subprojects.
> 
> This would
>  a) enable us to catch regressions in clang itself because the libomp (and libomptarget in the future) tests are triggered for each commit to clang
>  b) remove the necessity to rebuild clang separately for each commit to libomp which is quite time consuming and doesn't give full coverage of all commits to clang.

I agree. I think that we should also have separate in-tree and standalone builds for openmp given that there is a lot of stuff in the build system that depends on that. In summary:
i) llvm+clang+openmp in tree build with machine stable compiler
ii) standalone openmp build with the compiler built in i)
iii) standalone openmp build with the machine stable compiler

We could skip iii), but it is a fairly quick build. I don't mind working on a patch to do this on `ppc64le-nvidia-K40`. Was there any discussion to do that on the existing slave?

Thanks,
Samuel


https://reviews.llvm.org/D28492