public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
Date: Tue, 02 Aug 2022 03:56:34 +0000	[thread overview]
Message-ID: <bug-106345-4-sQLuJVEH4c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106345-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:ab1d329cb7d5ef19d234c37892c3268f063cf9c5

commit r11-10187-gab1d329cb7d5ef19d234c37892c3268f063cf9c5
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.

    (cherry picked from commit 75d20d6c84c12bedd65a904e462f02f0b9eb3f77)

  parent reply	other threads:[~2022-08-02  3:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 17:32 [Bug testsuite/106345] New: " mpolacek at gcc dot gnu.org
2022-07-19  6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
2022-07-20  2:01 ` linkw at gcc dot gnu.org
2022-07-25  5:53 ` cvs-commit at gcc dot gnu.org
2022-07-26 12:13 ` linkw at gcc dot gnu.org
2022-08-02  3:53 ` cvs-commit at gcc dot gnu.org
2022-08-02  3:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-02  3:58 ` cvs-commit at gcc dot gnu.org
2022-09-07  1:38 ` cvs-commit at gcc dot gnu.org
2022-09-13  5:21 ` cvs-commit at gcc dot gnu.org
2022-09-13  5:22 ` cvs-commit at gcc dot gnu.org
2022-09-13  6:23 ` cvs-commit at gcc dot gnu.org
2022-09-13  6:24 ` linkw at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106345-4-sQLuJVEH4c@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).