https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78319
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to ktkachov from comment #14)
> (In reply to Jakub Jelinek from comment #13)
> > So do you want something like:
> > /* { dg-skip-if "avoid conflicts with multilib options" { arm*-*-* } {
> > "-mcpu=*" } { "-mcpu=cortex-a15" } } */
> > /* { dg-additional-options "-mcpu=cortex-a15" { target arm*-*-* } } */
> > and remove the xfail?
> > cortex-a15 is randomly chosen non-cortex-m7 CPU, I don't know anything about
> > the ARM CPUs and what branch costs they have.
> > In any case, please resolve this soon, for a small testsuite glitch
> > (occassional XFAIL) keeping open P3 regression for so long is wasteful.
>
> I'd be happy with any tuning that makes this pass. I'll check with
> cortex-a15.
> Also, I suggest just using
> /* { dg-additional-options "-mtune=cortex-a15" { target arm*-*-* } } */
> That will use the cortex-a15 tuning (including BRANCH_COST) but will not
> enforce any architectural features, so should avoid the need for the
> multilib stuff
Unless people commonly use
RUNTESTFLAGS='--target_board=unix\{-mtune=cortex-a15,-mtune=cortex-m7\}' or
something similar, that might work well. The amount of tests that use -mtune=
in dg-options or dg-additional-options across all arches is big, so most likely
such RUNTESTFLAGS wouldn't be a very good idea.
