Florent DEFAY <spira.inhabitant@xxxxxxxxx> writes:
> some tests need to include standard header files, but we do not need
> to implement a libc
I don't know of a good way to handle this scenario. Most tests do not
use any header files, and it's reasonably easy to ignore the ones which
do. Or, it's also usually pretty easy to port newlib, which will at
least get you through the compilation tests.
> some tests are too long or use too large arrays and it is impossible
> with the memory of the machine
You can define STACK_SIZE while running the tests. That will disable
some large tests. I think this can be done in your site.exp file or
your board support file by setting target_info gcc,stack_size. See
gcc/testsuite/lib/gcc.exp for other target_info fields of interest.
The testsuite also supports a dg-require framework. For example, a test
marked with
/* { dg-require-effective-target int32plus } */
should not be run on a target with 16-bit ints. Poke around in
gcc/testsuite/lib/target-supports-exp.
I don't know if there is any documentation for this stuff, but there may
be.
Ian
