[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ86T=Xtjbv70_+Z_QC46apWwPcwR0u4E3q28k8+vqOZW1pesQ@mail.gmail.com>
Date: Thu, 25 Jun 2020 15:03:04 -0700
From: Andre McCurdy <armccurdy@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Release prep for 1.2.1, and afterwards
On Thu, Jun 25, 2020 at 2:51 PM Rich Felker <dalias@...c.org> wrote:
>
> On Thu, Jun 25, 2020 at 02:43:42PM -0700, Andre McCurdy wrote:
> > On Thu, Jun 25, 2020 at 1:50 PM Rich Felker <dalias@...c.org> wrote:
> > >
> > > As noted in the past I'd like to get rid of having high level flow
> > > logic in the arch asm and instead have the arch provide string asm
> > > fragments, if desired, to copy blocks, which could then be used in a
> > > shared C skeleton. However as you noted this has been a point of
> > > practical performance problem for a long time and I don't think it's
> > > fair to just keep putting it off for a better solution.
> >
> > I'd like to see the patches to enable asm memcpy for big endian ARM
> > merged. I may be the only user of musl on big endian ARM though (?) so
> > not sure how much wider interest there is.
>
> I'd forgotten I hadn't already merged it. However I was just rereading
> it and something looks amiss. Can you take a look again?
Is there anything in particular that looks wrong?
The most recent version of the patch still applies cleanly to master.
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.
