On 06/29/2011 06:55 AM, Richard Earnshaw wrote:
> 3. Add a new dg directive (perhaps dg-ignore-multilib) that instructs
> the framework to ignore the multilib options entirely (only supported
> for compile/assembly tests).
>
> There are a lot of target-specific tests that are not really testing
> execution, just that the compiler generates the right instruction under
> specific compilation options. It seems silly to force all this into the
> multi-lib framework.
If it's true that most testsuite runs on ARM include a default multilib,
then some tests can be skipped for everything other than the default
multilib and specify all the flags that are needed for the test, e.g.
with
/* { dg-require-effective-target default_multilib } */
That's much simpler than ignoring multilib flags, and avoids running
the same test multiple times with exactly the same options.
Janis
