On Friday 14 March 2008, Joseph S. Myers wrote:
> On Thu, 13 Mar 2008, Joel Sherrill wrote:
> > > Also, if you use a multilib option in testing, that option goes on the
> > > command line *after* the options specified in dg-options. The tests
> > > may need to use dg-skip-if to skip them if any CPU option other than
> > > the one in the test is explicitly specified (so it would be tested if
> > > no explicit -mcpu option is used, or if -mcpu=405 is the multilib
> > > option being tested).
> >
> > Are you thinking of something roughly like this?
> >
> > /* { dg-skip-if "" { { !-mcpu=405 } } { "*" } { "" } } */
>
> I'm thinking of
>
> /* { dg-skip-if "" { *-*-* } { "-mcpu=*" } { "-mcpu=405" } } */
I you have several of these you might want to consider adding an
effective-target check that uses a compile test rather than guessing from
commandline options. c.f. check_effective_target_arm32 and
check_effective_target_arm_vfp_ok.
Paul
