Re: How to adequately test 'sim' changes?

[fche at redhat dot com (Frank Ch. Eigler)]

cgd@sibyte.com (Chris G. Demetriou) writes:

: [...]
: I've got a bunch of sim changes that I'd like to submit in the next
: week or so [...]

Great.

: (1) What's the recommended method for testing 'sim' changes?  the
: sim subtree seems to have a minimal testsuite, but I was hoping for
: something more substantial?

For simulators without their own tests, we normally rely on the
cross-gcc and cross-gdb tests.  For this, you'd need to build the
remainder of the cross toolchain (compiler/binutils/debugger), and
run the respective tests against the sim.

: (2) which MIPS targets should be used for testing of
: architecture-dependent changes?

AFAIK, mipstx39-elf and mips64vr5000-elf are a reasonable pair.

: (3) which non-MIPS targets should be used for (additional) testing of
: architecture-independent changes?  (I'm not thinking anything big
: here, just the need for compile/smoke-test of minor additions.) [...]

The fr30, arm, mn10300, erc32 (sparc) would give reasonably wide
coverage for build-breakage testing.

: thanks!

No, thank you!  (I presume you know about the copyright
assignment/disclaimer procedure too.)


- FChE