https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78319
--- Comment #17 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #15)
> 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.
I think you're confusing ARM's use of -mtune with x86's. The x86 equivalent of
-mtune on ARM is -mcpu: it is rare to see -mtune in testsuite runs.
(On ARM there are two main options here -- -march and -mtune: -march selects
the permitted instructions; -mtune controls how to pick from within the
permitted set. -mcpu is a convenience option that controls both options at the
same time).
