public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: [PATCH roland/arm-memcpy] ARM: Make multiarch memcpy always use   NEON when compiler does
Date: Mon, 13 May 2013 23:12:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1305132312270.10338@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20130513224722.9F17C2C05E@topped-with-meat.com>

On Mon, 13 May 2013, Roland McGrath wrote:

> When the compiler is emitting NEON instructions anyway, there is no point
> in using IFUNC when we can just use the NEON memcpy unconditionally.
> 
> Tested on armv7l-linux-gnueabihf with CC='gcc -mfpu=neon',
> no check-abi failures, no regressions in 'make check subdirs=string'.

OK.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2013-05-13 23:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 22:47 Roland McGrath
2013-05-13 23:12 ` Joseph S. Myers [this message]
2013-05-14  7:47 ` Andreas Schwab
2013-05-17  0:31   ` Roland McGrath
2013-05-14 15:47 ` Richard Henderson
2013-05-17  0:32   ` Roland McGrath

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=Pine.LNX.4.64.1305132312270.10338@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=roland@hack.frob.com \
    /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).