|
From: Florian K. <br...@ac...> - 2011-10-10 22:30:23
|
On 10/10/2011 04:58 PM, Julian Seward wrote:
> On Saturday, October 08, 2011, Florian Krohm wrote:
>
> There are two different issues (not just for SSSE3, but for testing any
> instruction set extension):
>
> (1) can the assembler handle these instructions? If not, we can't build
> the relevant test cases. This is what the configure test checks for.
>
> (2) does the CPU support the instructions? If not, then we don't try
> to run the test cases. This is what x86_amd64_features tests.
>
Right, I understand. But we shouldn't be attempting to execute a test
that was not built. This is an issue of the make machinery, independent
of how it was determined whether the test can be built or whether the
hardware can execute it.
There are a few approaches
(1) Write the test in a way that it is independent of the tool chain
version (using .byte, .word etc instead of mnemonics). This is
what we've done for s390. But it's probably not feasible to recode
all existing testcases.
(2) Fix the make machinery to not execute the test if the executable
does not exist
(3) Have an implicit prereq that tests the existence of what is
specified in the prog: line
I haven't looked at how make regtest works but would guess that #3 might
be the simplest way to fix it.
> So maybe you have an old toolchain?
Not really:
GNU assembler (GNU Binutils for Ubuntu) 2.20.51-system.20100908
gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5
Florian
|