From: Segher Boessenkool <segher@kernel.crashing.org>
To: Aaron Sawdey <acsawdey@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, rs6000] don't use unaligned vsx for memset of less than 32 bytes
Date: Tue, 26 Jun 2018 16:01:00 -0000 [thread overview]
Message-ID: <20180626160116.GL16221@gate.crashing.org> (raw)
In-Reply-To: <979a1eeceb7c4c3f7b2068e9b924970760d695ff.camel@linux.ibm.com>
Hi!
On Mon, Jun 25, 2018 at 10:41:32AM -0500, Aaron Sawdey wrote:
> In gcc 8 I added support for unaligned vsx in the builtin expansion of
> memset(x,0,y). Turns out that for memset of less than 32 bytes, this
> doesn't really help much, and it also runs into an egregious load-hit-
> store case in CPU2006 components gcc and hmmer.
>
> This patch reverts to the previous (gcc 7) behavior for memset of 16-31
> bytes, which is to use vsx stores only if the target is 16 byte
> aligned. For 32 bytes or more, unaligned vsx stores will still be used.
> Performance testing of the memset expansion shows that not much is
> given up by using scalar stores for 16-31 bytes, and CPU2006 runs show
> the performance regression is fixed.
>
> Regstrap passes on powerpc64le, ok for trunk and backport to 8?
Yes, okay for both. Thanks!
Segher
> 2018-06-25 Aaron Sawdey <acsawdey@linux.ibm.com>
>
> * config/rs6000/rs6000-string.c (expand_block_clear): Don't use
> unaligned vsx for 16B memset.
prev parent reply other threads:[~2018-06-26 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 15:41 Aaron Sawdey
2018-06-26 16:01 ` Segher Boessenkool [this message]
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=20180626160116.GL16221@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=acsawdey@linux.ibm.com \
--cc=gcc-patches@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).