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/work154-dmf)] PowerPC: Make -mcpu=future enable -mblock-ops-vector-pair.
Date: Wed, 14 Feb 2024 23:12:29 +0000 (GMT)	[thread overview]
Message-ID: <20240214231229.ABD6C3861802@sourceware.org> (raw)

https://gcc.gnu.org/g:6b50854f0f0253619ed101789462d537f3d14416

commit 6b50854f0f0253619ed101789462d537f3d14416
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Tue Jan 23 00:16:58 2024 -0500

    PowerPC: Make -mcpu=future enable -mblock-ops-vector-pair.
    
    This patch re-enables generating load and store vector pair instructions when
    doing certain memory copy operations when -mcpu=future is used.
    
    During power10 development, it was determined that using store vector pair
    instructions were problematical in a few cases, so we disabled generating load
    and store vector pair instructions for memory options by default.  This patch
    re-enables generating these instructions if -mcpu=future is used.
    
    The patches have been tested on both little and big endian systems.  Can I check
    it into the master branch?
    
    2024-01-23   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
    
            * config/rs6000/rs6000-cpus.def (ISA_FUTURE_MASKS): Add
            -mblock-ops-vector-pair.
            (POWERPC_MASKS): Likewise.

Diff:
---
 gcc/config/rs6000/rs6000-cpus.def | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/config/rs6000/rs6000-cpus.def b/gcc/config/rs6000/rs6000-cpus.def
index 8754635f3d95..b6cd6d8cc847 100644
--- a/gcc/config/rs6000/rs6000-cpus.def
+++ b/gcc/config/rs6000/rs6000-cpus.def
@@ -90,6 +90,7 @@
 
 /* Flags for a potential future processor that may or may not be delivered.  */
 #define ISA_FUTURE_MASKS	(ISA_3_1_MASKS_SERVER			\
+				 | OPTION_MASK_BLOCK_OPS_VECTOR_PAIR	\
 				 | OPTION_MASK_FUTURE)
 
 /* Flags that need to be turned off if -mno-power9-vector.  */
@@ -127,6 +128,7 @@
 
 /* Mask of all options to set the default isa flags based on -mcpu=<xxx>.  */
 #define POWERPC_MASKS		(OPTION_MASK_ALTIVEC			\
+				 | OPTION_MASK_BLOCK_OPS_VECTOR_PAIR	\
 				 | OPTION_MASK_CMPB			\
 				 | OPTION_MASK_CRYPTO			\
 				 | OPTION_MASK_DFP			\

             reply	other threads:[~2024-02-14 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 23:12 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-23  5:21 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=20240214231229.ABD6C3861802@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).