[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200625081504.GE2048759@port70.net>
Date: Thu, 25 Jun 2020 10:15:04 +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-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
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..)
>
> and some more with open questions or work to be done that can't be
> finished now but should be revisited after release:
>
> - fenv overhaul (sorry for dropping this, Damian)
> - PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP
> - _SC_NPROCESSORS_{CONF,ONLN} behavior
> - hexagon port
> - rv32 port
> - arm fdpic (newly revived interest from users on list)
> - dni (dynamic linking without PT_INTERP absolute path) & related ldso
> work by rcombs
> - "lutimes: Add checks for input parameters"
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.
