I think you wrote this code ;). Anyway, the test selection is based on env['TARGET_ISA'] this ends up as the isa variable in tests/run.py. The isa variable is used to select the binary to use for the spec tests, so for ARM it will use 'arm'. Thus for each spec test, only one binary can be selected, although you might wan to have something other than a one-to-one TARGET to isa mapping, like i do in this case.
Ali On Mon, 26 Jul 2010 12:55:55 -0700, Steve Reinhardt begin_of_the_skype_highlighting end_of_the_skype_highlighting <ste...@gmail.com> wrote: > I'm confused... what exactly is the problem? Doesn't it work just to > create two independent tests? > > Steve > > On Mon, Jul 26, 2010 at 12:20 PM, Gabriel Michael Black > <gbl...@eecs.umich.edu> wrote: >> I don't think we/I found a good solution. I had (and may still have) >> copied >> and pasted versions of things with a 32 appended for SPARC, and x86 just >> doesn't have any 32 bit tests. The 32 bit SPARC tests may have just been >> in >> my own tree and never committed. >> >> Gabe >> >> Quoting Ali Saidi <sa...@umich.edu>: >> >>> >>> Hi Everyone, >>> >>> I'm trying to setup some regression tests for ARM at the moment. I've >>> got >>> two sets of binaries one for the thumb instruction set and another for >>> the >>> arm instruction set. Is there any way to setup a test for both? I think >>> we've run into this before but I don't know that we've ever solved the >>> problem (sparc32/sparc64; x86/x86-64; etc). If not I'm just going to >>> pick >>> the instructions for each test randomly. >>> >>> Thanks, >>> >>> Ali >>> _______________________________________________ >>> m5-dev mailing list >>> m5-dev@m5sim.org >>> http://m5sim.org/mailman/listinfo/m5-dev >>> >> >> >> >> _______________________________________________ >> m5-dev mailing list >> m5-dev@m5sim.org >> http://m5sim.org/mailman/listinfo/m5-dev >n _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
