mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Arm AArch64 port - search for interested people
Date: Mon, 24 Feb 2014 18:10:29 -0500	[thread overview]
Message-ID: <20140224231028.GF184@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140224183242.GE184@brightrain.aerifal.cx>

On Mon, Feb 24, 2014 at 01:32:42PM -0500, Rich Felker wrote:
> On Mon, Feb 24, 2014 at 12:22:22PM -0500, Strake wrote:
> > On 11/09/2013, Bortis Kevin <Kevin.Bortis@ruf.ch> wrote:
> > > Is someone interessted to help out with a musl ARM Aarch64 port? I got
> > > the message, that I will receive a dev board Q2/2014 for a new project,
> > > so I hope to have a working musl toolchain by then :)
> > 
> > I am interested. I shall ask an AMD A-series dev board sample when
> > available. I can likely start hacking this significantly next term,
> > from May. Is the status at
> > http://wiki.musl-libc.org/wiki/Porting/AArch64 accurate now?
> 
> I haven't followed efforts to port to aarch64, so I can't answer
> whether it's accurate. I just spent a few minutes looking at the
> partial port linker from the wiki
> (https://github.com/wermut/musl-aarch64) and it looks like a good bit
> of the work has been done and it might be fairly easy to finish it up.
> Either way, it would be great to have someone working on it again!

One thing to note: there seems to be some fishy stuff in the bits
headers we should check out, like whether blksize_t really needs to be
"int" (it's long on other systems), explicit use of "unsigned int"
instead of nlink_t without defining nlink_t to match, possibly-wrong
sysvipc structures (it looks like the legacy ones are being used
instead of the "64" ones, but I may be wrong), namespace issues in
bits/signal.h, ...

Rich


      parent reply	other threads:[~2014-02-24 23:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 11:38 Bortis Kevin
2013-09-11 12:58 ` Szabolcs Nagy
2013-09-11 16:51   ` Rich Felker
2013-09-11 17:53     ` Szabolcs Nagy
2013-09-12  2:11 ` Strake
2014-02-24 17:22 ` Strake
2014-02-24 18:17   ` Szabolcs Nagy
2014-02-24 18:32   ` Rich Felker
2014-02-24 22:48     ` Richard Pennington
2014-02-24 23:10     ` Rich Felker [this message]

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=20140224231028.GF184@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).