public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/work096)] Update ChangeLog.meissner. Date: Mon, 1 Aug 2022 22:12:54 +0000 (GMT) [thread overview] Message-ID: <20220801221254.CB4E0385802A@sourceware.org> (raw) https://gcc.gnu.org/g:1d8907484246602c8ddc52300e778e88aaeb1be6 commit 1d8907484246602c8ddc52300e778e88aaeb1be6 Author: Michael Meissner <meissner@linux.ibm.com> Date: Mon Aug 1 18:12:37 2022 -0400 Update ChangeLog.meissner. 2022-08-01 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 7549ae1606b..d0f8a782cc1 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,29 @@ +==================== work096, patch 1. + +Do not enable -mblock-ops-vector-pair. + +Testing has shown that using the load vector pair and store vector pair +instructions for block moves has some performance issues on power10. + +A patch on June 11th modified the code so that GCC would not set +-mblock-ops-vector-pair by default if we are tuning for power10, but it +would set the option if we were tuning for a different machine and have +load and store vector pair instructions enabled. + +This patch eliminates the code setting -mblock-ops-vector-pair. If you +want to generate load vector pair and store vector pair instructions for +block moves, you must use -mblock-ops-vector-pair. + + +2022-08-01 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000.cc (rs6000_option_override_internal): Remove + code setting -mblock-ops-vector-pair. + +==================== work096, create branch. + 2022-08-01 Michael Meissner <meissner@linux.ibm.com> Clone branch
next reply other threads:[~2022-08-01 22:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-01 22:12 Michael Meissner [this message] 2022-08-02 0:38 Michael Meissner 2022-08-02 4:26 Michael Meissner 2022-08-02 18:00 Michael Meissner 2022-08-02 18:50 Michael Meissner 2022-08-02 19:35 Michael Meissner 2022-08-02 21:34 Michael Meissner 2022-08-03 15:14 Michael Meissner 2022-08-03 15:36 Michael Meissner 2022-08-04 22:50 Michael Meissner
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=20220801221254.CB4E0385802A@sourceware.org \ --to=meissner@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).