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 21:54:19 +0000 (GMT) [thread overview] Message-ID: <20221117215420.00214384F6D3@sourceware.org> (raw) https://gcc.gnu.org/g:351194afe0231d20d1321bf24446b2a0dfdc688f commit 351194afe0231d20d1321bf24446b2a0dfdc688f Author: Michael Meissner <meissner@linux.ibm.com> Date: Mon Nov 14 19:59:48 2022 -0500 Update ChangeLog.meissner. 2022-11-14 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 3fa2264624b..df595d768f6 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,26 @@ +==================== Dmf004 branch, patch #20. + +Use lxvl and stxvl for small variable memcpy moves. + +This patch adds support to generate inline code for block copy with a variable +size if the size is 16 bytes or less. If the size is more than 16 bytes, just +call memcpy. + +To handle variable sizes, I found we need DImode versions of the two insns for +copying memory (cpymem<mode> and <movmem<mode>). + +2022-11-14 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000-string.cc (expand_block_move): Add support for + using lxvl and stxvl to move up to 16 bytes inline without calling + memcpy. + * config/rs6000/rs6000.md (cpymem<mode>): Expand cpymemsi to also + provide cpymemdi to handle DImode sizes as well as SImode sizes. + (movmem<mode>): Expand movmemsi to also provide movmemdi to handle + DImode sizes as well as SImode sizes. + ==================== Dmf004 branch, patch #17. Support load/store vector with right length.
next reply other threads:[~2022-11-17 21:54 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-17 21:54 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: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 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=20221117215420.00214384F6D3@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: linkBe 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).