This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PING][PATCH] Change contrib/test_installed for testing cross compilers
- From: Jeff Law <law at redhat dot com>
- To: Alan Lawrence <alan dot lawrence at arm dot com>, Steve Ellcey <sellcey at imgtec dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 25 Nov 2014 09:55:25 -0700
- Subject: Re: [PING][PATCH] Change contrib/test_installed for testing cross compilers
- Authentication-results: sourceware.org; auth=none
- References: <daea6fb7-5a10-46dc-99c6-b70b30418053 at BAMAIL02 dot ba dot imgtec dot org> <54736224 dot 1030809 at arm dot com>
On 11/24/14 09:51, Alan Lawrence wrote:
Having just been experimenting with testing of installed compilers - yes
something like this could be useful, however: to do cross-testing I
found I also (a) had to set my target_list; so either an extra flag for
that, or maybe just a generic 'extra_site_flags' parameter?
(b) I had to set up some boards...so maybe could have got there with the
--tmpdir flag, ok;
(c) lost all the parallelism provided by the Makefile in build/gcc. It
should be possible to use the (check-parallel-xxx rules from) Makefile
in conjunction with the site.exp from contrib/test_installed, haven't
got that far yet...
This does leave me wondering (1) whether a one-step "$ test_installed"
is feasible, or a two-stage setup and then run is inevitable; (2)
whether having all that parallelism expressed in the Makefile is the
best place for it. Not that I have an alternative proposal at this point...
It might be inevitable to have a two stage setup. Red Hat does
installed compiler testing and I'm sure increased parallelism for
install testing would be appreciated by the team doing that work.
As for the --target, change itself, seems reasonable.
Jeff