From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: Thinking about release
Date: Sun, 14 Jul 2013 01:37:57 -0500 [thread overview]
Message-ID: <1373783877.20031.7@driftwood> (raw)
In-Reply-To: <20130710194233.GD29800@brightrain.aerifal.cx> (from dalias@aerifal.cx on Wed Jul 10 14:42:34 2013)
On 07/10/2013 02:42:34 PM, Rich Felker wrote:
> On Wed, Jul 10, 2013 at 09:28:21AM +1200, Andre Renaud wrote:
> > >> Does anyone have any comments on the suitability of this code,
> or what
> > >
> > > If nothing else, it fails to be armv4 compatible. 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...?
> >
> > Rob Landley mentioned a while ago that armv4 has issues with the
> EABI
> > stuff. Is armv4 a definite lower bound for musl support, as opposed
> to
> > armv4t or armv5?
>
> EABI specifies thumb; however, it's possible to have code which
> conforms fully to EABI but does not rely on the presence of thumb. GCC
> is incapable of generating such code, but it could be enhanced to do
> so, and all of the existing assembly in musl is plain-v4-compatible,
> so I would prefer not to shut out the possibility of supporting older
> ARM.
One of my larger pending todo items for aboriginal is fishing the last
gplv2 release out of gcc git the same way I did for binutils. (In
theory, this should give me armv7l support. In practice, the mpfr and
gmp split complicates matters...)
If somebody wanted to come up with an armv4-eabi patch, I'd happily
include it. Or just give me rather a lot of hints on what would be
involved, since I'm not much of an arm assembly programmer...
Rob
next prev parent reply other threads:[~2013-07-14 6:37 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 [this message]
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=1373783877.20031.7@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).