Date: Mon, 24 Feb 2014 18:10:29 -0500 From: Rich Felker <dalias@...ifal.cx> To: musl@...ts.openwall.com Subject: Re: Arm AArch64 port - search for interested people 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@....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
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.