[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 25 Jun 2020 19:31:25 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: Release prep for 1.2.1, and afterwards
* Rich Felker <dalias@...c.org> [2020-06-25 11:39:36 -0400]:
> On Thu, Jun 25, 2020 at 10:15:04AM +0200, Szabolcs Nagy wrote:
> > * Rich Felker <dalias@...c.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)
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.
