From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Release prep for 1.2.1, and afterwards
Date: Thu, 25 Jun 2020 17:51:17 -0400 [thread overview]
Message-ID: <20200625215117.GU6430@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAJ86T=VabfSDvNRnVtJvPB_7m2fVEr0F1PPoL5FmHtxQtCMqnw@mail.gmail.com>
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@libc.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?
Rich
next prev parent reply other threads:[~2020-06-25 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 20:42 Rich Felker
2020-06-24 22:39 ` Jeffrey Walton
2020-06-25 8:15 ` Szabolcs Nagy
2020-06-25 15:39 ` Rich Felker
2020-06-25 17:31 ` Szabolcs Nagy
2020-06-25 20:50 ` Rich Felker
2020-06-25 21:15 ` Rich Felker
2020-06-26 1:20 ` Rich Felker
2020-06-26 8:40 ` Szabolcs Nagy
2020-07-06 22:12 ` Rich Felker
2020-07-07 15:00 ` Szabolcs Nagy
2020-07-07 17:22 ` Rich Felker
2020-07-07 18:20 ` Szabolcs Nagy
2020-06-25 21:43 ` Andre McCurdy
2020-06-25 21:51 ` Rich Felker [this message]
2020-06-25 22:03 ` Andre McCurdy
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=20200625215117.GU6430@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).