From: Andre Renaud <andre@bluewatersys.com>
To: Rich Felker <dalias@aerifal.cx>
Cc: musl@lists.openwall.com
Subject: Re: Thinking about release
Date: Thu, 11 Jul 2013 16:04:21 +1200 [thread overview]
Message-ID: <CAPfzE3ZMGwEvs2n_4LCKzMv0FROS55_1N+HdBw7HgNhexgM+eA@mail.gmail.com> (raw)
In-Reply-To: <20130711033754.GL29800@brightrain.aerifal.cx>
Hi Rich,
>> Rich - do you have any comments on whether either the C or assembler
>> variants of memcpy might be suitable for inclusion in musl?
>
> I would say either might be, but it looks like if we want competitive
> performance, some asm will be needed (either inline or full). My
> leaning would be to go for something simpler than the asm you've been
> experimenting with, but with same or better performance, if this is
> possible. I realize the code is not that big as-is, in terms of binary
> size, but it's big from an "understanding it" perspective and I don't
> like big asm blobs that are hard for somebody to look at and say "oh
> yeah, this is clearly right".
>
> Anyway, the big questions I'd still like to get answered before moving
> forward is whether the cache line alignment has any benefit.
I certainly appreciate the need for concise, well understood, easily
readable code.
I can't see any obvious reason why this shouldn't work, although the
assembler as it stands makes pretty heavy use of all the registers,
and I can't immediately see how to rework it to free up 2 more (I can
free up 1 by dropping the attempted preload). Given my (lack of)
skills with ARM assembler, I'm not sure I'll be able to look too
deeply into either of these options, but I'll have a go at the inline
ASM version to force 8*4byte loads to see if it improves things.
Regards,
Andre
next prev parent reply other threads:[~2013-07-11 4:04 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 [this message]
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
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=CAPfzE3ZMGwEvs2n_4LCKzMv0FROS55_1N+HdBw7HgNhexgM+eA@mail.gmail.com \
--to=andre@bluewatersys.com \
--cc=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).