This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Running contrib/config-list.mk from the buildbots


On 19 November 2013 18:20, Diego Novillo <dnovillo@google.com> wrote:

> Right, because you're using 4.8.  These warnings disappear when using
> trunk and/or do not actually break the build.  I suppose this is too
> much for the buildbot then?  It won't have a recent trunk around, so
> perhaps restricting it to the targets that actually build with 4.8 is
> the way to go.

No, that will likely get you the empty set.
The most repeatable results are obtained by using the source tree under test
to bootstrap a native compiler on the host first.  If you use one massive host
to run all of config-list.mk, that extra preparation generally doesn't make
all that much difference (unless you happen to have a host with # of cores
similar to # of test targets).

If you run these tests on a host that also occaisonally does native bootstrap
tests, you could extend that script to specify a --prefix and install
the compiler
if it's good.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]