From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Thinking about release
Date: Wed, 12 Jun 2013 21:43:14 -0400 [thread overview]
Message-ID: <20130613014314.GC29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPfzE3a0h=2NFqgnBqXj3J2q7VgYjqZ19Ab=0LAe5u5SvWXHaA@mail.gmail.com>
On Thu, Jun 13, 2013 at 01:33:16PM +1200, Andre Renaud wrote:
> Hi Rich,
>
> > Most of the other major items left on the agenda since the last
> > release are probably not going to happen right away unless there's a
> > volunteer to do them (zoneinfo, cpuset/affinity, string functions
> > cleanup, C++ ABI matching, ARM-optimized memcpy) and one, the ld.so
> > symlink direction issue, still requires some serious discussion and
> > decision-making.
>
> Regarding the ARM-optimisations - I am happy to have a go at providing
> a cleaned up implementation, although I can't recall what the final
> consensus was on how this should be implemented. A simple ARMv4
I think the first step should be benchmarking on real machines.
Somebody tried the asm that was posted and claimed it was no faster
than musl's C code; I don't know the specific hardware they were using
and I don't even recall right off who made the claim or where it was
reported, but I think before we start writing or importing code we
need to have a good idea how the current C code compares in
performance to other "optimized" implementations.
> implementation would cover all the bases, providing near universal
> support, although would obviously not support the more modern
> platforms. Is there any intention to move the base level support up to
> ARMv5? I would consider that reasonable, given the age of ARMv4.
> Alternatively, should we have multiple implementations
> (ARMv4/ARMv5/ARMv7), and choose between them either at compile or
> run-time?
It's possible to branch based on __hwcap at runtime, if this would
really help.
> Obviously this stuff is probably not destined for the immediate
> release, but more likely for the one after that.
Yes, this looks like it will be a process that takes some time to sort
out the facts and then tune the code.
For what it's worth, I just did my first runs of libc-bench on real
ARM hardware (well, an FPGA-based ARM). memset is half the speed of
glibc's, but strchr and strlen are about 40% faster than glibc's. I
don't think libc-bench is really a good benchmark as of yet, so we
should probably develop more detailed tests.
Rich
next prev parent reply other threads:[~2013-06-13 1:43 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 [this message]
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
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=20130613014314.GC29800@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).