[Openmp-dev] libomp buildbots

[Hahnfeld, Jonas via Openmp-dev]

Hi,

I see that the build type has been switched to Release+Asserts.
Is there any ongoing plan about triggering libomp builds by clang commits or integrating libomp into the other clang buildbots?

Cheers
Jonas

> -----Original Message-----
> From: Openmp-dev [mailto:openmp-dev-bounces at lists.llvm.org] On Behalf
> Of Jack Howarth via Openmp-dev
> Sent: Wednesday, March 23, 2016 2:41 PM
> To: Alexey Bataev
> Cc: gkistanova at gmail.com; LLVM-OpenMP (openmp-dev at lists.llvm.org)
> Subject: Re: [Openmp-dev] libomp buildbots
> 
> On Wed, Mar 23, 2016 at 3:19 AM, Alexey Bataev via Openmp-dev <openmp-
> dev at lists.llvm.org> wrote:
> > Agree, but still it is better to build the compiler from scratch to
> > catch possible regressions in clang. Currently there are no other
> > buildbots that execute tests from libomp testsuite. Or openmp runtime
> > and its tests must be added to other buidbots
> >
> > Best regards,
> > Alexey Bataev
> > =============
> > Software Engineer
> > Intel Compiler Team
> >
> 
> Aren't there any buildbots which perform 3-stage bootstraps with file
> comparisons? Wouldn't it be simpler to just add openmp to the projects
> sources on such a buildbot and adjust the test suite run there to include
> libomp? That approach would insure that libomp is being built with the same
> compiler compiler for a given revision.
> 
> > 23.03.2016 9:53, Dmitri Gribenko пишет:
> >> 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
> >>
> >
> > _______________________________________________
> > Openmp-dev mailing list
> > Openmp-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5868 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20160331/f86d0afa/attachment.bin>