This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: libsanitizer merge from upstream r196090
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Uros Bizjak <ubizjak at gmail dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "H.J. Lu" <hjl dot tools at gmail dot com>, Dodji Seketeli <dodji at redhat dot com>, Marek Polacek <polacek at redhat dot com>, Dmitry Vyukov <dvyukov at google dot com>, Evgeniy Stepanov <eugenis at google dot com>, Alexey Samsonov <samsonov at google dot com>
- Date: Thu, 5 Dec 2013 16:23:03 +0400
- Subject: Re: libsanitizer merge from upstream r196090
- Authentication-results: sourceware.org; auth=none
- References: <CAFULd4ZrFy-o7GmDh31WRpoxiYwwLpaAY6pOtxCZ9i-+4kfv1A at mail dot gmail dot com> <CAGQ9bdzMRvFOWXmAbRoXAM4otn6JMR8AALspJ1s=hP=jgm7KXQ at mail dot gmail dot com> <CAFULd4Z-HrnYedyH_fcH1knQAD+=4jmC_xOBacgs2-DJhGWD0Q at mail dot gmail dot com> <CAGQ9bdz4Qm8nGJhLPJ9wwP71rUC4CddaReqWsbUqLq-GZSqRTA at mail dot gmail dot com> <20131203114959 dot GW892 at tucnak dot redhat dot com> <CAGQ9bdwvEB7-TGoycetGmMOqs6Xe=uW0bVn8KAWMooaSYe6nUQ at mail dot gmail dot com> <20131203154709 dot GA892 at tucnak dot redhat dot com> <529E09FB dot 30901 at redhat dot com> <CAGQ9bdwbHuHLEjQKtoZhDDMNp9_bUeSYksGr3K8F_av8_D=D9A at mail dot gmail dot com> <529F9918 dot 7080803 at redhat dot com> <CAGQ9bdyN1FVZ_VLiyR41oU_BOPtEcoveAOT5uRPD3fNN1uuE0A at mail dot gmail dot com>
On Thu, Dec 5, 2013 at 4:22 PM, Konstantin Serebryany
<konstantin.s.serebryany@gmail.com> wrote:
> On Thu, Dec 5, 2013 at 1:05 AM, Jeff Law <law@redhat.com> wrote:
>> On 12/03/13 22:08, Konstantin Serebryany wrote:
>>>
>>> We need
>>> a) patches that we can review and apply to the llvm repository (w/o
>>> breaking the modern systems, of course)
>>> b) a buildbot that would run 24/7 catching regressions.
>>>
>>> If we reach a green state for a platform X and have a buildbot for it,
>>> keeping it green will require relatively small effort.
>>> Every time we break it we will notice it in minutes and fix quickly
>>> while we still have the same context fresh.
>>> Fixing old systems once in few months during merge to gcc is costly
>>> because failures accumulate.
>>
>> I'm well overbooked already. However, if you have x86/x86_64 systems in
>> your build farm that can be virtualized,
>
> Unfortunately we don't.
> In case anyone wants to provide their build machines and maintain a
> bot on them here are the instructions
Actual link: http://llvm.org/docs/HowToAddABuilder.html
> (Evgeniy and Alexey in CC may be able to help)
>
> --kcc
>
>> I can help set up a suitable VM.
>> CentOS 5.x is old enough to trigger lots of interesting problems, but is
>> still in widespread use.
>>
>> Jeff
>>
>>