From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: Thinking about release
Date: Wed, 10 Jul 2013 14:38:36 -0500 [thread overview]
Message-ID: <1373485116.27613.40@driftwood> (raw)
In-Reply-To: <20130709053711.GO29800@brightrain.aerifal.cx> (from dalias@aerifal.cx on Tue Jul 9 00:37:12 2013)
On 07/09/2013 12:37:12 AM, Rich Felker wrote:
> On Tue, Jul 09, 2013 at 05:06:21PM +1200, Andre Renaud wrote:
> > The git tree is available here:
> >
> https://github.com/AndreRenaud/musl/commit/713023e7320cf45b116d1c29b6155ece28904e69
>
> It's an open question whether it's better to sync something like this
> with an 'upstream' or adapt it to musl coding conventions. Generally
> musl uses explicit instructions rather than pseudo-instructions/macros
> for prologue and epilogue, and does not use named labels.
Do your own local version. You can always copy ideas from other
projects if "upstream" changes later.
> > Does anyone have any comments on the suitability of this code, or
> what
>
> If nothing else, it fails to be armv4 compatible.
Query: did you ever implement a non-thumb version of armv4 eabi
support? I remember some discussion about it being possible, I don't
remember the outcome.
> Fixing that should
> not be hard, but it would require a bit of an audit. The return
> sequences are the obvious issue, but there may be other instructions
> in use that are not available on armv4 or maybe not even on armv5...?
I've beaten armv4-only, armv4t-only, and armv5-only modes out of qemu.
That's the reason for the first half of my versatile patch:
http://landley.net/hg/aboriginal/file/1612/sources/patches/linux-arm.patch
> > kind of more rigorous testing could be applied?
>
> See above.
>
> What also might be worth testing is whether GCC can compete if you
> just give it a naive loop (not the fancy pseudo-vectorized stuff
> currently in musl) and good CFLAGS. I know on x86 I was able to beat
> the fanciest asm strlen I could come up with simply by writing the
> naive loop in C and unrolling it a lot.
Duff's device!
Rob
next prev parent reply other threads:[~2013-07-10 19:38 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
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 [this message]
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=1373485116.27613.40@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).