[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160118112530.GB9621@port70.net>
Date: Mon, 18 Jan 2016 12:25:30 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Open/pending issues as of Jan 17
* Rich Felker <dalias@...c.org> [2016-01-17 18:15:54 -0500]:
> With a quick review of the mailing list since late November I found
> the following possibly-open issues:
>
> - resolver search domain support
> - preinit_array
> - mlock2 syscall wrapper
> - mips siginfo_t fix
i think this should have priority
(abi visible bug, should not wait for arch/bits cleanup)
> - avl tree: any changes still pending??
there are no known bugs in the current code, but
tsearch_small.c would be an improvement over it.
(and twalk,tfind should be separate tu)
> - adding pot file for translators
> - unsetenv pointer eval after free
> - printf big widths/precisions
> - atomic.h overhaul
> - dirent.h macros
> - dlopen deadlock
> - setvbuf
random stuff:
- linux 4.* uapi (includes mlock2, but a lot of other stuff too)
- symbol versioning (for at least gcc-6 libgcc_s.so)
- __cxa_thread_atexit_impl ? (i expect this to come up in real code)
- stdatomic.h
- string functions correctness
- regex bre extensions \+ \? \|
- regcomp increase tre_stack_new limit
- str{f,p}time %z %Z %k %l ?
- noreturn __assert_fail ?
- hidden visibility for internal functions
- compiler builtins in libc (sqrt, fabs, memcpy..)
- asm -> inline asm
- ld128 math
> Also, not code issues, but the following possibly-open documentation
> issues were found:
>
> - documenting atomic.h primitives contracts
> - documenting "known UB" in musl
>
> There were a few other patches that were mostly trivial which I just
> committed outright, and the big one, out-of-tree builds, that I
> finally committed after some more testing.
>
> Is there anything else I missed that's an open issue right now? Or
> requests for prioritizing the above list? I'm going to try to take the
> above (and anything else that comes up) and turn it into a plan for
> what can reasonably go into the next release.
>
> Rich
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.
