[Openmp-dev] libomp buildbots

[Dmitri Gribenko via Openmp-dev]

On Tue, Mar 22, 2016 at 11:51 PM, Hahnfeld, Jonas
<Hahnfeld at itc.rwth-aachen.de> wrote:
>> -----Original Message-----
>> From: Alexey Bataev [mailto:a.bataev at hotmail.com]
>> Sent: Wednesday, March 23, 2016 6:12 AM
>> To: Dmitri Gribenko
>> Cc: LLVM-OpenMP (openmp-dev at lists.llvm.org); gkistanova at gmail.com;
>> Peyton, Jonathan L (jonathan.l.peyton at intel.com); Hahnfeld, Jonas
>> Subject: Re: libomp buildbots
>>
>> Hi,
>> I don't think this a good idea to not use latest clang compiler. There might be
>> some changes, that may have bugs. Currently these bugs may be revealed
>> during testing of OpenMP runtime on libomp buildbots.
>> But definitely we must switch to Release+Asserts version of build.
>
> If we want to use it like this, it would be a good idea to actually trigger a libomp build when something gets committed to clang. I think right now, only commits to openmp do that which would make it difficult to spot the error if clang broke...

I wouldn't be opposed to that.  My current concern is that libomp is
duplicating the work (building the compiler) that other jobs running
on the same host do anyway.

Dmitri

-- 
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/