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/work119)] Update ChangeLog.meissner
Date: Mon,  1 May 2023 17:24:15 +0000 (GMT)	[thread overview]
Message-ID: <20230501172415.7E99C3858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:6702108df42f9135e32cdffdaae8055122b0bafc

commit 6702108df42f9135e32cdffdaae8055122b0bafc
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Mon May 1 13:24:12 2023 -0400

    Update ChangeLog.meissner

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 85bfbce8419..7a3f8e4b578 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,33 @@
+==================== Branch work119, patch #130 ====================
+
+Split vec_extract from memory before reload for V16QI/V8HI/V4SI with constant elements.
+
+This patch goes through the support function rs6000_adjust_vec_address and the
+functions it calls to allow them to be called before register allocation.  The
+places that take a scratch register will allocate a new pseudo register if they
+are passed a SCRATCH register.
+
+It then changes the vec_extract support for V16QI/V8HI/V4SI with constant
+element numbers to be split before register allocation.
+
+2023-04-27   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000.cc (get_vector_offset): Allow function to be
+	called before register allocation.
+	(adjust_vec_address_pcrel): Likewise.
+	(rs6000_adjust_vec_address): Likewise.
+	* config/rs6000/vsx.md (vsx_extract_<mode>_load): Split before register
+	allocation.
+	(vsx_extract_v4si_load_to_<su>di): Likewise.
+	(vsx_extract_<VSX_EXTRACT_I2:mode>_load_to_u<GPR:mode>): Likewise.
+	(*vsx_extract_v8hi_load_to_s<mode>): Likewise.
+	(vsx_extract_<mode>_var_load): Likewise.
+	(vsx_extract_v4si_var_load_to_<su>di): Likewise.
+	(vsx_extract_<VSX_EXTRACT_I2:mode>_var_load_to_u<GPR:mode>): Likewise.
+	(vsx_extract_v8hi_var_load_to_s<mode>): Likewise.
+
 ==================== Branch work119, patch #127 ====================
 
 Optimize variable element vec_extract to be converted to floating point

             reply	other threads:[~2023-05-01 17:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 17:24 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-29  4:10 Michael Meissner
2023-04-28 19:48 Michael Meissner
2023-04-28  6:37 Michael Meissner
2023-04-28  3:44 Michael Meissner
2023-04-28  3:37 Michael Meissner
2023-04-26 23:55 Michael Meissner
2023-04-26 23:44 Michael Meissner
2023-04-26 16:21 Michael Meissner
2023-04-26 15:47 Michael Meissner
2023-04-26  5:14 Michael Meissner
2023-04-25 15:56 Michael Meissner
2023-04-25  2:55 Michael Meissner
2023-04-25  2:04 Michael Meissner
2023-04-25  2:03 Michael Meissner
2023-04-21 19:01 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=20230501172415.7E99C3858D28@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).