Re: new port's validation

[Ian Lance Taylor <iant@google.com>]

Florent DEFAY <spira.inhabitant@gmail.com> writes:

>> 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.
>
> I cannot find any site.exp file. Can you give me a tree example for
> another arch?

When run "make check-gcc" it will create a site.exp file.  If there is
an existing site.exp file, it will be edited to preserve whatever values
are already there.


> I did not find anything looking like defining target_info in .exp files but only
> using target_info. Where should I add a board support file?

I've never figured out how this is supposed to work cleanly, if indeed
such a thing was ever defined.  I just add new files to the baseboards
directory in the dejagnu tree, e.g., /usr/share/dejagnu/baseboards.


>> 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.
>
> How to tell the testsuite that my target is 16-bit? I found that in
> target-supports.exp:
> proc check_effective_target_int32plus { } {
>     return [check_no_compiler_messages int32plus object {
>         int dummy[sizeof (int) >= 4 ? 1 : -1];
>     }]
> }
>
> Is it cross-compiled and executed code? Because execution is not
> configured (simulator not configured).

That code is not executed, it is simply cross-compiled.  The compilation
will fail if sizeof(int) < 4 because dummy[-1] is a compilation error.

Ian