From: Szabolcs Nagy <nsz@port70.net>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Release prep for 1.2.1, and afterwards
Date: Thu, 25 Jun 2020 19:31:25 +0200 [thread overview]
Message-ID: <20200625173125.GF2048759@port70.net> (raw)
In-Reply-To: <20200625153936.GP6430@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2020-06-25 11:39:36 -0400]:
> On Thu, Jun 25, 2020 at 10:15:04AM +0200, Szabolcs Nagy wrote:
> > * Rich Felker <dalias@libc.org> [2020-06-24 16:42:44 -0400]:
> >
> > > I'm about to do last work of merging mallocng, followed soon by
> > > release. Is there anything in the way of overlooked bug reports or
> > > patches that should still be addressed in this release cycle?
> > >
> > > Things I'm aware of:
> > >
> > > - "Proposal to match behaviour of gethostbyname to glibc". Latest
> > > patch is probably ok, but could be deferred to after release.
> > >
> > > - nsz's new sqrt{,f,l}. I'm hesitant to do all three right away
> > > without time to test, but replacing sqrtl.c could be appropriate
> > > since the current one is badly broken on archs with ld wider than
> > > double. However it would need to accept ld80 in order not to be
> > > build-breaking on m68k, or m68k would need an alternative.
> >
> > that's still under work
>
> Won't it work just to make it decode/encode the ldshape, and otherwise
> use exactly the same code? Or are there double-rounding issues if the
> quad code is used with ld80?
i think the same code may work for ld80 too,
but i'm still testing the single/double/quad
code, it's not ready for inclusion.
> > but it would be nice if we could get the aarch64
> > memcpy patch in (the c implementation is really
> > slow and i've seen ppl compare aarch64 vs x86
> > server performance with some benchmark on alpine..)
>
> OK, I'll look again.
thanks.
(there are more aarch64 string functions in the
optimized-routines github repo but i think they
are not as important as memcpy/memmove/memset)
next prev parent reply other threads:[~2020-06-25 17:31 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 [this message]
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
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=20200625173125.GF2048759@port70.net \
--to=nsz@port70.net \
--cc=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).