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/dmf004)] Update ChangeLog.meissner.
Date: Tue, 15 Nov 2022 21:24:12 +0000 (GMT)	[thread overview]
Message-ID: <20221115212412.E5BB6393BA60@sourceware.org> (raw)

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

commit ece06cb8df9e4265cf02ac8346a5f4c40b7c359a
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Tue Nov 15 16:23:42 2022 -0500

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index b755a0044ac..01dfa7e2868 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,17 @@
+==================== Dmf004 branch, patch #22.
+
+Allow for inline code for memcpy to move more than 16 bytes.
+
+2022-11-15   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-string.cc (toplevel): Include optabs.h.
+	(expand_block_move_variable): New helper function, move variable byte
+	copy support here.  Add support to move more than 16 bytes.
+	(expand_block_move): Move variable copy support to
+	expand_block_move_variable.
+
 ==================== Dmf004 branch, patch #21.
 
 Add parameter for memcpy inline code moves

             reply	other threads:[~2022-11-15 21:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 21:24 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-17 22:32 Michael Meissner
2022-11-17 21:56 Michael Meissner
2022-11-17 21:55 Michael Meissner
2022-11-17 21:55 Michael Meissner
2022-11-17 21:55 Michael Meissner
2022-11-17 21:55 Michael Meissner
2022-11-17 21:55 Michael Meissner
2022-11-17 21:55 Michael Meissner
2022-11-17 21:54 Michael Meissner
2022-11-17 21:54 Michael Meissner
2022-11-17 21:54 Michael Meissner
2022-11-17 21:54 Michael Meissner
2022-11-17 21:53 Michael Meissner
2022-11-17 21:53 Michael Meissner
2022-11-17 21:52 Michael Meissner
2022-11-17 20:06 Michael Meissner
2022-11-17  5:15 Michael Meissner
2022-11-16 20:57 Michael Meissner
2022-11-16 18:55 Michael Meissner
2022-11-16 18:12 Michael Meissner
2022-11-16  8:30 Michael Meissner
2022-11-15 18:55 Michael Meissner
2022-11-15 17:29 Michael Meissner
2022-11-15  1:00 Michael Meissner
2022-11-12  3:49 Michael Meissner
2022-11-11 23:16 Michael Meissner
2022-11-09 22:40 Michael Meissner
2022-11-09  5: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=20221115212412.E5BB6393BA60@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).