mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: ARM optimisations
Date: Mon, 04 Mar 2013 12:55:01 -0600	[thread overview]
Message-ID: <1362423301.29250.16@driftwood> (raw)
In-Reply-To: <20130302062102.GP20323@brightrain.aerifal.cx> (from dalias@aerifal.cx on Sat Mar  2 00:21:02 2013)

On 03/02/2013 12:21:02 AM, Rich Felker wrote:
> > systems aren't that common. (They existed, the tin can tools nail
> > board used one, but the generic C code works for them. Point is I'm
> > not sure they're worth _optimizing_ for if it costs the vast
> > majority of systems a 25% performance hit and we don't want to
> > maintain multiple versions. If you _have_ an armv5 version, the
> > armv4 one won't/shouldn't get much testing.)
> 
> Can you explain why you think a version that's v4 compatible will be
> that much slower? If so, v5 code can be used as long as it checks
> __hwcap and falls back to a simple working version...

Alas, I do not have recent benchmarks. The timesys guys benched various  
stuff in 2006 and that's where I grabbed the 25% figure. I mostly test  
under qemu, where benchmarks are meaningless for real hardware.

If I'm in error, ignore me.

Rob

  reply	other threads:[~2013-03-04 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 23:15 Andre Renaud
2013-02-28 23:30 ` Rich Felker
2013-03-02  4:33   ` Rob Landley
2013-03-02  6:21     ` Rich Felker
2013-03-04 18:55       ` Rob Landley [this message]
2013-03-02 11:34     ` Szabolcs Nagy
2013-03-02 20:33       ` Andre Renaud

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=1362423301.29250.16@driftwood \
    --to=rob@landley.net \
    --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).