This is the mail archive of the
mailing list for the GCC project.
Re: GCC Buildbot
- From: Martin Liška <mliska at suse dot cz>
- To: Paulo Matos <firstname.lastname@example.org>, gcc at gcc dot gnu dot org
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, dje dot gcc at gmail dot com
- Date: Mon, 25 Sep 2017 11:52:50 +0200
- Subject: Re: GCC Buildbot
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com>
Thank you for working on that! To be honest, I've been running local buildbot on
my desktop machine which does builds your buildbot instance can do (please see:
- doing time to time (once a week) sanitizer builds: ASAN, UBSAN and run test-suite
- doing profiled bootstrap, LTO bootstrap (yes, it has been broken for quite some time) and LTO profiled bootstrap
- building project with --enable-gather-detailed-mem-stats
- doing coverage --enable-coverage, running test-suite and uploading to a location: https://gcc.opensuse.org/gcc-lcov/
- similar for Doxygen: https://gcc.opensuse.org/gcc-doxygen/
- periodic building of some projects: Inkscape, GIMP, linux-kernel, Firefox - I do it with -O2, -O2+LTO, -O3, ...
Would be definitely fine, but it takes some care to maintain compatible versions of a project and GCC compiler.
Plus handling of dependencies of external libraries can be irritating.
- cross build for primary architectures
That's list of what I have and can be inspiration for you. I can help if you want and we can find a reasonable resources
where this can be run.
Apart from that, I fully agree with octoploid that http://toolchain.lug-owl.de/buildbot/ is duplicated effort which is running
on GCC compile farm machines and uses a shell scripts to utilize. I would prefer to integrate it to Buildbot and utilize same
GCC Farm machines for native builds.
Another inspiration (for builds) can come from what LLVM folks do:
Anyway, it's good starting point what you did and I'm looking forward to more common use of the tool.