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/work091)] Update ChangeLog.meissner.
Date: Thu, 16 Jun 2022 21:44:41 +0000 (GMT)	[thread overview]
Message-ID: <20220616214441.DE6663850217@sourceware.org> (raw)

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

commit f737d9d3df39a98d7da97df3d901b71b0d45c30f
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Jun 9 19:25:40 2022 -0400

    Update ChangeLog.meissner.
    
    2022-06-09   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
            * ChangeLog.meissner: Update.

Diff:
---
 gcc/ChangeLog.meissner | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index ab8c8a9b517..17a72bb7eab 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,20 @@
+==================== patch work091/work001
+
+Disable generating load/store vector pairs for block copies.
+
+Testing has found that using store vector pair for block copies can result
+in a slow down on power10.  This patch disables using the vector pair
+instructions for block copies if we are tuning for power10.
+
+2022-06-09   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+	* config/rs6000/rs6000.cc (rs6000_option_override_internal): Do
+	not generate block copies with vector pair instructions if we are
+	tuning for power10.
+
+==================== New branch.
+
 2022-06-09   Michael Meissner  <meissner@linux.ibm.com>
 
 	Clone branch


             reply	other threads:[~2022-06-16 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 21:44 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-16 21:44 Michael Meissner
2022-06-13 17:06 Michael Meissner
2022-06-13 17:03 Michael Meissner
2022-06-09 23:26 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=20220616214441.DE6663850217@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: 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).