This is the mail archive of the
sid@sources.redhat.com
mailing list for the SID project.
Re: Testing with --target=FOO
- To: Ben Elliston <bje at redhat dot com>
- Subject: Re: Testing with --target=FOO
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- Date: Fri, 11 May 2001 07:20:02 -0400
- Cc: sid at sources dot redhat dot com
- References: <15099.34487.665129.623361@scooby.apac.redhat.com>
Hi -
bje wrote:
: When --target= is specified to sid's configure script, the sid
: Makefiles build generic components and components related to that
: target. [...]
: This causes problems when testing builds with --target specified.
: Many of the generic components require a CPU component as part of the
: simulation to be tested. [...]
Which ones? Back when we only had an arm model to work with, we
were expedient and hard-coded tests to use that. But now, with
many more ports in-house, those old tests should generally be
made cpu-independent, or replicated in multiple cpu-dependent
copies, as appropriate.
: Ideas I have had thus far (in increasing order of preference):
:
: + Mark such tests as "untested".
Maybe.
: + Build a small dummy CPU component that can be compiled
: unconditionally. This will take time to write and may not be
: adequate for the kinds of tests we need to do.
Nah.
: + Build the arm7t model unconditionally, regardless of the target.
: Only the cpu is required as far as I can tell.
Can you provide more details on why some canonical cpu is required
for what are presumably non-cpu tests?
or #4:
+ Change the test suite.
- FChE
PGP signature