> 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
>
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
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
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 appende
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 :
Hi E
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 so
