[Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
cvs-commit at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Mon Jul 25 05:53:01 GMT 2022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:
https://gcc.gnu.org/g:75d20d6c84c12bedd65a904e462f02f0b9eb3f77
commit r13-1818-g75d20d6c84c12bedd65a904e462f02f0b9eb3f77
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Mon Jul 25 00:51:44 2022 -0500
rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345]
As PR106345 shows, when configuring compiler with an explicit
option --with-tune=<value>, 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 <cpu> as tune as the one specified by -mdejagnu-cpu.
2022-07-25 Peter Bergner <bergner@linux.ibm.com>
Kewen Lin <linkw@linux.ibm.com>
PR testsuite/106345
gcc/ChangeLog:
* config/rs6000/rs6000.h (DRIVER_SELF_SPECS): Adjust -mdejagnu-cpu
to filter out all -mtune options.
More information about the Gcc-bugs
mailing list