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: Thu, 17 Nov 2022 20:06:18 +0000 (GMT)	[thread overview]
Message-ID: <20221117200618.778183852C59@sourceware.org> (raw)

https://gcc.gnu.org/g:679d1ff882c19a3c6abcbbf33b9c9c9d07919f21

commit 679d1ff882c19a3c6abcbbf33b9c9c9d07919f21
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Nov 17 15:06:03 2022 -0500

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index c72f248797d..3186721cb64 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,21 @@
+==================== Dmf004 branch, patch #28.
+
+Add suuport to use stxvl for variable sized memsets.
+
+2022-11-17   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-protos.h (expand_block_set): Add declaration.
+	* config/rs6000/rs6000-string.cc (expand_block_set): New support for
+	optimizing variable sized memsets.
+	* config/rs6000/rs6000.md (setmem<mode>): Add setmemdi along with
+	setmemsi.  Add support for optimizing memsets of other bytes than just
+	0.  Add support for using stxvl to support variable sized sets.
+	* config/rs6000/rs6000.opt (--param rs6000-memcpy-inline-bytes): Make
+	the default 16, not 32.
+	((--param rs6000-memset-inline-bytes): New parameter.
+
 ==================== Dmf004 branch, patch #27.
 
 Fix lxvl and stxvl wrong conditional branch.

             reply	other threads:[~2022-11-17 20:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 20:06 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  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 21:24 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=20221117200618.778183852C59@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).