mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Thinking about release
Date: Tue, 23 Jul 2013 23:48:44 -0400	[thread overview]
Message-ID: <20130724034843.GP3249@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPfzE3bq-f8id1M7fD5p8dMe8uEuZrNMfcrFPVi-jr-xVpKWdg@mail.gmail.com>

On Wed, Jul 24, 2013 at 01:34:07PM +1200, Andre Renaud wrote:
> Hi Rich,
> 
> On 12 July 2013 16:16, Rich Felker <dalias@aerifal.cx> wrote:
> > By the way, I also did some tests with misaligning the src/dest with
> > respect to cache lines. and the timing did change, but not in any way
> > I could make sense of...
> >
> > It may turn out to be that the issues are sufficiently complex that we
> > won't get ideal performance without either copying the BSD code you
> > suggested or fully understanding what it's doing, and other ARM
> > performance issues, and developing something new based on that
> > understanding... In that case copying/adapting the BSD code might turn
> > out to be the right solution for now.
> 
> What was the final decision on this? The last version (with mixed
> inline assembler/C) is (I believe) relatively readable, and appears to
> be correct. It also compiles on all the available platforms (ie:
> armv4+). Can this version be accepted?

It looks buggy as-is; as far as I can tell, it will crash if src/dest
are aligned with respect to each other but not aligned mod 4, i.e. the
code starts out copying word-at-a-time rather than byte-at-a-time.

I think the C version would be acceptable if we get the bugs fixed and
test it well, but I'd also like to still keep the asm under
consideration. There are lots of cases not covered by the C version,
like misaligned copies (important for strings, not for much else). Do
you think these cases are important?

Rich


  reply	other threads:[~2013-07-24  3:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  1:25 Rich Felker
2013-06-13  1:33 ` Andre Renaud
2013-06-13  1:43   ` Rich Felker
2013-07-09  5:06     ` Andre Renaud
2013-07-09  5:37       ` Rich Felker
2013-07-09  6:24         ` Harald Becker
2013-07-09 21:28         ` Andre Renaud
2013-07-09 22:26           ` Andre Renaud
2013-07-10  6:42             ` Jens Gustedt
2013-07-10  7:50               ` Rich Felker
2013-07-10 22:44             ` Andre Renaud
2013-07-11  3:37               ` Rich Felker
2013-07-11  4:04                 ` Andre Renaud
2013-07-11  5:10                   ` Andre Renaud
2013-07-11 12:46                     ` Rich Felker
2013-07-11 22:34                       ` Andre Renaud
2013-07-12  3:16                         ` Rich Felker
2013-07-12  3:36                           ` Andre Renaud
2013-07-12  4:16                             ` Rich Felker
2013-07-24  1:34                               ` Andre Renaud
2013-07-24  3:48                                 ` Rich Felker [this message]
2013-07-24  4:40                                   ` Andre Renaud
2013-07-28  8:09                                     ` Rich Felker
2013-07-11  5:27                 ` Daniel Cegiełka
2013-07-11 12:49                   ` Rich Felker
2013-07-15  4:25                 ` Rob Landley
2013-07-10 19:42           ` Rich Felker
2013-07-14  6:37             ` Rob Landley
2013-07-11  4:30           ` Strake
2013-07-11  4:33             ` Rich Felker
2013-07-10 19:38         ` Rob Landley
2013-07-10 20:34           ` Andre Renaud
2013-07-10 20:49             ` Nathan McSween
2013-07-10 21:01             ` Rich Felker
2013-06-13 15:46 ` Isaac
2013-06-26  1:44 ` Rich Felker
2013-06-26 10:19   ` Szabolcs Nagy
2013-06-26 14:21     ` Rich Felker

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=20130724034843.GP3249@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).