public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Will Newton <will.newton@linaro.org>
Cc: libc-ports@sourceware.org, patches@linaro.org
Subject: Re: [PATCH v2] ARM: Add Cortex-A15 optimized NEON and VFP memcpy routines, with IFUNC.
Date: Wed, 17 Apr 2013 15:40:00 -0000	[thread overview]
Message-ID: <516EC27E.8080502@twiddle.net> (raw)
In-Reply-To: <516D18F0.4060009@linaro.org>

On 2013-04-16 11:25, Will Newton wrote:
>   ports/sysdeps/arm/armv7/multiarch/Makefile         |   3 +

Does this really require v7?  From a brief read I didn't see anything in the 
_arm version that didn't work since v5te (ldrd and pld).  Any reason not to put 
this into armv6 instead?

> +ENTRY(memcpy)
> +	.type	memcpy, %gnu_indirect_function
> +	ldr	r1, .Lmemcpy_arm
> +	tst	r0, #HWCAP_ARM_NEON
> +	it	ne
> +	ldrne	r1, .Lmemcpy_neon
> +	bne	1f

Swap vfp and neon tests and you don't need the branch.

> +.Lreturn:

Unused label?

> +	ldr	tmp1, [src, #-60]	/* 15 words to go.  */
> +	str	tmp1, [dst, #-60]

These negative offsets mean thumb2 doesn't work.  That's fine, but it means 
that you need care for this in the _arm case.

You have two choices: either do the swapping to arm mode by hand in the impl 
file, or force the entire memcpy.o to arm mode by using #define NO_THUMB at the 
top, before the #include <sysdep.h>.

If you chose the later, then you don't have to worry about thumb2's restriction 
on rd=rn when rm=pc, and can avoid the extra move.  And the then unnecessary it 
markup.


r~

  reply	other threads:[~2013-04-17 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  9:25 Will Newton
2013-04-17 15:40 ` Richard Henderson [this message]
2013-04-17 15:53   ` Will Newton
2013-04-18  7:42     ` Richard Henderson
2013-04-18  7:47       ` Siddhesh Poyarekar
2013-04-18  7:54         ` Will Newton
2013-04-18  8:26           ` Siddhesh Poyarekar
2013-04-18  8:38             ` Will Newton
2013-04-18 17:58             ` Siddhesh Poyarekar
2013-04-22  8:27               ` Will Newton
2013-04-17 17:51 ` Carlos O'Donell
2013-04-18  8:01   ` Will Newton
2013-04-19 21:47 ` Joseph S. Myers
2013-04-22  8:32   ` Will Newton

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=516EC27E.8080502@twiddle.net \
    --to=rth@twiddle.net \
    --cc=libc-ports@sourceware.org \
    --cc=patches@linaro.org \
    --cc=will.newton@linaro.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).