testsuite: effective_target_march_option: support checking for -march=*
authorHans-Peter Nilsson <hp@axis.com>
Sun, 19 Jan 2020 19:38:06 +0000 (20:38 +0100)
committerHans-Peter Nilsson <hp@axis.com>
Sun, 19 Jan 2020 19:38:06 +0000 (20:38 +0100)
commit3684bbb022cd75da55e1457673f269980aa12cdf
treee26b25120e7ca7f3ffece793fdbe15bbea781827
parent0042bafd4b5eb85ee9610b9558d7b7f00579888c
testsuite: effective_target_march_option: support checking for -march=*

* lib/target-supports.exp (effective_target_march_option): New.

I see no (other) way to, depending on the absence of an option,
add an option for a specific target.

For gcc.dg/torture/pr26515.c and cris-elf, you get an error for
supplying multiple (different) -march=... options (where that
error is desirable), like testing cris-elf with
RUNTESTFLAGS=--target_board=cris-sim/arch=v8, where otherwise
-march=v10 and -march=v8 will both be given, and the test would
fail.

For historians, this was accidentally misordered and committed after
the (first) patch using march_option.  Oops.
gcc/testsuite/ChangeLog
gcc/testsuite/lib/target-supports.exp