public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: leonardo.sandoval.gonzalez@linux.intel.com
To: libc-alpha@sourceware.org
Cc: hjl.tools@gmail.com,
	Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Subject: [PATCH] x86-64: remove duplicate line on PREFETCH_ONE_SET macro
Date: Tue, 15 May 2018 17:13:00 -0000	[thread overview]
Message-ID: <20180515171303.11312-1-leonardo.sandoval.gonzalez@linux.intel.com> (raw)

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

Tested on 64-bit AVX machine

       	  * sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S (MEMMOVE):
 	  remove duplicate line on PREFETCH_ONE_SET macro

Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
---
 sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S b/sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S
index cbd0d077cf6..1404131bb71 100644
--- a/sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S
+++ b/sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S
@@ -90,7 +90,6 @@
 #  define PREFETCH_ONE_SET(dir, base, offset) \
 	PREFETCH ((offset)base); \
 	PREFETCH ((offset + dir * PREFETCH_SIZE)base); \
-	PREFETCH ((offset + dir * PREFETCH_SIZE)base); \
 	PREFETCH ((offset + dir * PREFETCH_SIZE * 2)base); \
 	PREFETCH ((offset + dir * PREFETCH_SIZE * 3)base)
 # else
-- 
2.17.0

             reply	other threads:[~2018-05-15 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 17:13 leonardo.sandoval.gonzalez [this message]
2018-05-15 18:32 ` Florian Weimer
2018-05-15 18:47   ` Leonardo Sandoval
2018-05-16 17:03   ` Leonardo Sandoval
2018-05-16 17:04     ` Florian Weimer

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=20180515171303.11312-1-leonardo.sandoval.gonzalez@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.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).