From 75d20d6c84c12bedd65a904e462f02f0b9eb3f77 Mon Sep 17 00:00:00 2001 From: Peter Bergner Date: Mon, 25 Jul 2022 00:51:44 -0500 Subject: [PATCH] rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345] As PR106345 shows, when configuring compiler with an explicit option --with-tune=, it would cause some test cases to fail if their test points are sensitive to tune setting, such as: group_ending_nop, loop align etc. It doesn't help that even to specify one explicit -mcpu=. This patch is to adjust the behavior of -mdejagnu-cpu by filtering out all -mcpu= and -mtune= options, then test cases would use as tune as the one specified by -mdejagnu-cpu. 2022-07-25 Peter Bergner Kewen Lin PR testsuite/106345 gcc/ChangeLog: * config/rs6000/rs6000.h (DRIVER_SELF_SPECS): Adjust -mdejagnu-cpu to filter out all -mtune options. --- gcc/config/rs6000/rs6000.h | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/gcc/config/rs6000/rs6000.h b/gcc/config/rs6000/rs6000.h index 7d04556304a..ad9bf0f7358 100644 --- a/gcc/config/rs6000/rs6000.h +++ b/gcc/config/rs6000/rs6000.h @@ -81,12 +81,15 @@ # define SUBTARGET_DRIVER_SELF_SPECS "" #endif -/* Only for use in the testsuite: -mdejagnu-cpu= simply overrides -mcpu=. +/* Only for use in the testsuite: -mdejagnu-cpu= filters out all + -mcpu= as well as -mtune= options then simply adds -mcpu=, + while -mdejagnu-tune= filters out all -mtune= options then + simply adds -mtune=. With older versions of Dejagnu the command line arguments you set in - RUNTESTFLAGS override those set in the testcases; with this option, - the testcase will always win. Ditto for -mdejagnu-tune=. */ + RUNTESTFLAGS override those set in the testcases; with these options, + the testcase will always win. */ #define DRIVER_SELF_SPECS \ - "%{mdejagnu-cpu=*: %