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/work133)] Update ChangeLog.meissner
Date: Thu, 31 Aug 2023 02:08:36 +0000 (GMT)	[thread overview]
Message-ID: <20230831020836.E5D163858D20@sourceware.org> (raw)

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

commit c68f9b7c13939db7d7630971001bdd4e18617567
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Aug 30 22:08:31 2023 -0400

    Update ChangeLog.meissner

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index bf1659f17de3..e25ac8a0d896 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,44 @@
+==================== Branch work133, patch #2 ====================
+
+Add -mno-lxvp and -mno-stxvp.
+
+This patch adds the options -mno-lxvp and -mno-stxvp that control whether GCC
+will generate vector pair load/stores or split the instructions into separate
+vector loads/stores.  These switches are not documented, but are there to allow
+us to look at some places where the paired load/store instructions slow things
+down.
+
+With this patch, GCC will not allow X-form (register + register) vector
+pair loads or stores unless both lxvp and stxvp are being generated.
+
+I also added the lxvp and stxvp command line options to the options that the
+user can enable or disable with #pragma target or attribute target.
+
+The default is to generate the vector pair load/store instructions.
+
+2023-08-30  Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/mma.md (movoo): Add support for -mno-lxvp and
+	-mno-stxvp.
+	* config/rs6000/rs6000.cc (rs6000_debug_reg_global): If -mdebug=reg,
+	print out whether we are generating lxvp and/or stxvp instructions.
+	(rs6000_option_override_internal): Warn if -mlxvp or -mstxvp was used
+	without -mmma being set.
+	(rs6000_setup_reg_addr_masks structure): Add support for -mno-lxvp and
+	-mno-stxvp.
+	(rs6000_opt_vars): Add lxvp and stxvp command line options.
+	* config/rs6000/rs6000.md (isa attribute): Add lxvp and stxvp isa
+	support.
+	(enabled attribute): Likewise.
+	* config/rs6000/rs6000.opt (-mlxvp): New option.
+	(-mstxvp): Likewise.
+
+gcc/testsuite/
+
+	* gcc.target/powerpc/p10-lxvp-stxvp.c: New test.
+
 ==================== Branch work133, patch #1 ====================
 
 Replace UNSPEC_COPYSIGN with copysign RTL

             reply	other threads:[~2023-08-31  2:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  2:08 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-31  0:58 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=20230831020836.E5D163858D20@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).