|
Message-ID: <005901cf9553$a5460f50$efd22df0$@codeaurora.org> Date: Tue, 1 Jul 2014 10:41:10 -0700 From: "Weiming Zhao" <weimingz@...eaurora.org> To: <musl@...ts.openwall.com> Subject: RE: AArch64 merge back Hi Isaac, So if I just want to use some arch-independent functions, then I just need to build the main musl repo with aarch64 compiler. Is my understanding correct? Thanks, Weiming -----Original Message----- From: Isaac Dunham [mailto:ibid.ag@...il.com] Sent: Monday, June 30, 2014 6:45 PM To: musl@...ts.openwall.com Subject: Re: [musl] AArch64 merge back On Mon, Jun 30, 2014 at 06:14:36PM -0700, Weiming Zhao wrote: > Hi Isaac, > > Do you mean those arch independent functions (e.g. abs, sprint, > memcpy) have already been merged? No, I was asking if you meant the whole port-in-progress or if you were only asking about said functions; at that point I had not checked. At present, I can tell you what the git log says: -memcpy.c was last touched in August last year implementing a portable optimized memcpy. -abs.c has not changed in the 3 years of git history -sprintf.c (I assume that's what you mean by 'sprint'?) has not been touched since 2012. ...all of which are before AArch64 porting. Is the relevant code in 'rebase-1.0'? Thanks, Isaac Dunham > -----Original Message----- > From: Isaac Dunham [mailto:ibid.ag@...il.com] > Sent: Monday, June 30, 2014 5:07 PM > To: musl@...ts.openwall.com > Subject: Re: [musl] AArch64 merge back > > On Mon, Jun 30, 2014 at 03:56:45PM -0700, Weiming Zhao wrote: > > Hi, > > I'm wondering if there is any plan to merge back the changes for > > AArch64 from https://github.com/crxz0193/musl-aarch64 ? > > > > So we can stay on the main repository. > > What's the status of that? I see commits related to a few syscalls > from the end of March/April 1, and nothing newer. > The last news I heard, some of the work that would be needed was done, > but I did not get the impression that it was possible to build working > binaries, even static ones. > (If this is incorrect, I'd like to hear the current status.) > > Some ports have been merged before all functionality worked (including > the dynamic linker), but I don't recall seeing any ports get merged > before it was possible to produce a working executable. > > Or are you referring to just the non-arch-specific changes? > > Thanks, > Isaac Dunham > >
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.